I've encountered a problem with a function that used to work in remote WinRM SSL sessions. Recently, my code no longer performs as expected due to the latest Windows 11 October 24h2 cumulative update, specifically KB5066835. The line of code that creates an update searcher is now throwing an 'Access is denied' error. Previously, this code worked flawlessly, but now I've had to resort to using psexec and exporting updates to an object with Export-Clixml, then reloading the results with Import-Clixml. I've also noticed that the PSWindowsUpdate module can't scan during remote sessions anymore, which is a new limitation since installations have always required a local session. I couldn't find any documentation on this change, and I'm looking for any insights or workarounds.
2 Answers
It seems like the October cumulative update has really messed with PSRemoting. Many of us are experiencing similar issues. I rolled back KB5066835, and that restored functionality to the API for me.
Exactly! It's like they keep adding layers of complexity instead of just fixing bugs.
I thought remote access was never fully supported for certain functions, which is why we've been using workarounds like Invoke-Command for the PSWindowsUpdate module. I learned something new today!
Yeah, many of us thought the same. It’s surprising that they would enforce new restrictions like this.
Right? It just adds more hassle for those of us who rely on remote scripting.
Yeah, it’s frustrating when updates break existing features. Microsoft really needs to tighten up their patches.