Windows 11 Update KB5053598 Broke pshell

[Bob]

Windows 11 Update KB5053598 broke pshell [and who knows what else ] on my system so I promptly uninstalled it.

Executing commands like:

pshell /s "(gcim win32_operatingsystem).LastBootUpTime"
pshell /s "(Invoke-WebRequest ifconfig.me/ip).Content.Trim()"
pshell /s "(get-date)-(gcim win32_operatingsystem).LastBootUpTime"​

in either TakeCommand or TCC led to a short delay followed by an abrupt closure of the window.

The event log contained entries like the following.

Faulting application name: TCC.EXE, version: 34.1.27.0, time stamp: 0x67b77619
Faulting module name: ntdll.dll, version: 10.0.26100.3323, time stamp: 0xfacafff0
Exception code: 0xc0000409
Fault offset: 0x00000000001236c6
Faulting process id: 0x37AC
Faulting application start time: 0x1DB94F22CB9F2F5
Faulting application path: C:\Program Files\JPSoft\TCMD34\TCC.EXE
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll​

FWIW there are many many reports of other problems associated with KB5053598 [which should have warned me not to install it.]

ALSO following the uninstall -- visiting Windows Update again started an automatic download of KB5053598 and I had to pause updates to stop it.

My system details

TCC 34.01.27 x64 Windows 11 [Version 10.0.26100.3194]
TCC Build 27 Windows 11 Build 26100

Device DellG15
Processor AMD Ryzen 7 7840HS w/ Radeon 780M GraphicsFWIW
Memory 16.0 GB (15.3 GB usable)​

 

[vefatica]

I'm OK on Windows 10 (was updated Tuesday). I can execute two of your three examples ... no crashes.

v:\> pshell /s "(Invoke-WebRequest ifconfig.me/ip).Content.Trim()"
74.111.37.137

v:\> pshell /s "(gcim win32_operatingsystem).LastBootUpTime"

Thursday, March 13, 2025 11:00:18



v:\> pshell /s "(get-date)-(gcim win32_operatingsystem).LastBootUpTime"
PSHELL: System.Management.Automation.ParseException : At line:1 char:57
+ "(get-date)-(gcim win32_operatingsystem).LastBootUpTime"?
+                                                         ~◙Unexpected token '?' in expression or statement.

v:\> ver
TCC 34.01.27 x64 (d:\tc34\tcc.exe)
Microsoft Windows 10 Pro for Workstations
10.0.19045.5608 (2009, 22H2)
WindowsTerminal 1.23.2502.04003 (preview) (1.23.353.0)

 

[Bob]

I'm OK on Windows 10 (was updated Tuesday). I can execute two of your three examples ... no crashes.

v:\> pshell /s "(Invoke-WebRequest ifconfig.me/ip).Content.Trim()"
74.111.37.137

v:\> pshell /s "(gcim win32_operatingsystem).LastBootUpTime"

Thursday, March 13, 2025 11:00:18



v:\> pshell /s "(get-date)-(gcim win32_operatingsystem).LastBootUpTime"
PSHELL: System.Management.Automation.ParseException : At line:1 char:57
+ "(get-date)-(gcim win32_operatingsystem).LastBootUpTime"?
+                                                         ~◙Unexpected token '?' in expression or statement.

v:\> ver
TCC 34.01.27 x64 (d:\tc34\tcc.exe)
Microsoft Windows 10 Pro for Workstations
10.0.19045.5608 (2009, 22H2)
WindowsTerminal 1.23.2502.04003 (preview) (1.23.353.0)

Didn’t know that KB5053598 was for Windows 10 also. I thought it only applied to “Windows 11 version 24H2, all editions”. Live and learn.

However all three examples have always worked on both Windows 11 before this “update” and Windows 10.

>pshell /s "(gcim win32_operatingsystem).LastBootUpTime"

Friday, March 14, 2025 10:16:31 AM

 

[mdlawler]

Windows 11 Update KB5053598 broke pshell [and who knows what else ] on my system so I promptly uninstalled it.

Executing commands like:

pshell /s "(gcim win32_operatingsystem).LastBootUpTime"​

pshell /s "(Invoke-WebRequest ifconfig.me/ip).Content.Trim()"​

pshell /s "(get-date)-(gcim win32_operatingsystem).LastBootUpTime"​

in either TakeCommand or TCC led to a short delay followed by an abrupt closure of the window.

The event log contained entries like the following.

Faulting application name: TCC.EXE, version: 34.1.27.0, time stamp: 0x67b77619​

Faulting module name: ntdll.dll, version: 10.0.26100.3323, time stamp: 0xfacafff0​

Exception code: 0xc0000409​

Fault offset: 0x00000000001236c6​

Faulting process id: 0x37AC​

Faulting application start time: 0x1DB94F22CB9F2F5​

Faulting application path: C:\Program Files\JPSoft\TCMD34\TCC.EXE​

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll​

FWIW there are many many reports of other problems associated with KB5053598 [which should have warned me not to install it.]

ALSO following the uninstall -- visiting Windows Update again started an automatic download of KB5053598 and I had to pause updates to stop it.

My system details

TCC 34.01.27 x64 Windows 11 [Version 10.0.26100.3194]​

TCC Build 27 Windows 11 Build 26100​

​

Device DellG15​

Processor AMD Ryzen 7 7840HS w/ Radeon 780M GraphicsFWIW​

Memory 16.0 GB (15.3 GB usable)​

I'm also seeing this. Exception code: 0xc0000409 means that Windows detected a possible stack overflow. Either Microsoft has turned this on for more applications or they have introduced problems with this stack checking code or they have actually introduced possible stack overflows or perhaps something I haven't thought of. Hopefully Rex will have ideas.

 

[vefatica]

That KB5053598 is problematic seems to be well known. Google for "KB5053598" and check out the top stories.

 

[rconn]

I can reproduce that here. Unfortunately, it's not in the TCC code and there's nothing I can do to fix it.

Unclear yet whether the issue is with Microsoft / Powershell changes, or with the Powershell library that TCC is using to execute strings & scripts. The library is no longer distributed or supported, there is no source code, and the developers are gone. (It also doesn't know about Powershell 7 or Core.) Windows is throwing a series of exceptions deep (as in REALLY deep) in the Windows dll's.

So unless Microsoft issues a patch that restores the functionality, I'll need to either find another library that allows C++ / Powershell integration, or remove the Powershell code from TCC.

 

[Bob]

I can reproduce that here. Unfortunately, it's not in the TCC code and there's nothing I can do to fix it.
. . . . . . . . .
. . . . . . . . .
So unless Microsoft issues a patch that restores the functionality, I'll need to either find another library that allows C++ / Powershell integration, or remove the Powershell code from TCC.

Thanks for your reply and explanation of the problem. This apparent Windows 11 regression or bug is aggravating but it illustrates how much we depend on your expertise to deal with the vagaries of the Microsoft release cycle!