Windows Update killed PSU installation - why?

PowerShell Universal
1

On Nov, 2nd, the server carrying my PSU 4.3.9 installation, made a reboot after a Edge-Upgrade at 2 AM. After this, it does not work as expected. In the system log, I found some details in the system log:
2024-11-02 02:08:48.268 +01:00 [ERR] API process did not start in 30 seconds.
…
2024-11-02 02:09:20.064 +01:00 [ERR] API process did not start in 30 seconds.
…
2024-11-02 02:09:23.247 +01:00 [ERR] Failed to create admin account.
…
2024-11-02 02:09:35.034 +01:00 [ERR] Dashboard process running but not response after 10 seconds. Terminating process.
…
After that, all calls to an authenticating API function fails, and I can’t login any more (Failed to communicate with security service.)

I tried a reboot, dism and sfc repairs, an update to 4.4.1 - but no change.

In a newer log, I found an unhandled exception:
System.InvalidOperationException: Provide Authority, MetadataAddress, Configuration, or ConfigurationManager to OpenIdConnectOptions

So for now, I have no idea what to do. I would appreciate any advise.

Kind regards,
Frank

2

Do you know which update it was that was installed? Maybe there’s a clue there.

3

The reboot was triggered because of PendingFileRenameOperations with ??\C:\Program Files (x86)\Microsoft\EdgeUpdate\1.3.195.27

I could not find other traces of install operations. So there is nothing I could try to uninstall.

4

That’s just the updater for Edge - not an update to Edge itself. You sure nothing else changed in the environment? Like, maybe a service account password or a certificate expiring?

5

Well, there are changes, even if I’m not always aware of them. Towards your question: the certificate for the https access is unchanged, and I get the login page without security warning. The service is running as local system. When I restart the service, there are no error messages or even warnings in application, system or security event log.

Is it possible to increase the debug level for the PSU log files (how)?

Following your words, I discovered a change in the netsh winttp setting. And wow, PSU contacts our proxy-server:
1730817123.201 0 10.100.100.118 TCP_DENIED/407 4023 CONNECT localhost:49930 - HIER_NONE/- text/html
1730817129.238 0 10.100.100.118 TCP_DENIED/407 4023 CONNECT localhost:49899 - HIER_NONE/- text/html

and tries to get in touch with “localhost”. Our netsh config is quite simple and should be correct:
PS C:\WINDOWS\system32> netsh winhttp show proxy

Aktuelle WinHTTP-Proxyeinstellungen:

Proxyserver     :  proxy-zen-10.spielbankennds.nds:3128
Umgehungsliste  :  <local>

Is there a way to tell PSU not to contact the proxy while trying to talk to itself?

6

Is it possible to increase the debug level for the PSU log files (how)?

You can adjust the logging level in the appsettings.json file.
Look at Logging | PowerShell Universal for instructions on how.

Is there a way to tell PSU not to contact the proxy while trying to talk to itself?

You may be able to do this by following Module | PowerShell Universal to set the API access URL, also in appsettings.json

7

Year, I was able to fix the problem by setting the env variable NO_PROXY. Thanks for your help.

1 Like