WSUSTemp power profile stays active / monitor always on

[LogicDaemon]

Hi.

1. I'm often updating new Win7 machines with
   

   Code: Select all

   cmd\DoUpdate.cmd /nobackup /updatercerts /updatecpp /updatetsc /skipieinst /autoreboot

   
   and, sometimes, with
   

   Code: Select all

   cmd\DoUpdate.cmd /nobackup /updatercerts /updatecpp /instdotnet35 /instdotnet4 /updatetsc /skipieinst /autoreboot

   
   
   And I found that occasionally (I guess, 3 times out of 10) after installing all updates and multiple reboots, it cleans up for itself (like removing WSUSTempAdmin user and its profile, and removing scripts from Windows dir), but it keeps power profile "WSUSTemp" active, which causes monitor to never turn off.
   
   I can't reliably reproduce the effect, but I'm sure it's not some side-effects of other software or power losses (because wsusoffline runs on clean machine right after installing drivers, and it's powered over an UPS).
   
   One thing may be related: sometimes I run wsusoffline while being connected over RDP.
   
   
2. can you change that WSUSTemp power profile so monitor will turn off after some duration, instead of keeping it always on? There is sense for doing this even during that 2-4 hours when updates are being installed. I understand why it's introduced at all – because otherwise windows goes to sleep while installing updates, and then requires password on wake up. But turning off the monitor in 2-5 minutes will not cause workstation lock, but it will lower power consumption and prolong monitor life. It's even more reasonable on a notebook, where putting display to sleep will add 20-300% of battery time (which may be useful if power will go down during updates installation).

[LogicDaemon]

just happened to me on freshly installed Win10 with

Code: Select all

cmd\DoUpdate.cmd /nobackup /updatercerts /updatecpp /instdotnet35 /instdotnet4 /updatetsc /skipieinst

wsusoffline either found no updates or installed one, but quit very quickly – in less than a minute. After that, power profile WSUSTemp stayed active.

log contains nothing specific
http://pastie.org/10905147

[sephron]

Bump.

Same issue, with WOU v10.8 on a brand new HP EliteBook running win7 x64.

I work at a full-service MSP and we use WSUS Offline as part of our pre-configuration process, preparing new machines to be delivered to clients... Thank you, btw. WSUS Offline allows us to deliver new machines a full day earlier than we could otherwise!

I just got a call from a client who received a brand new laptop this morning and he asked me whether this computer was new or refurbished. We only sell new hardware. He told me that he left the laptop open on his desk, running on battery power, while he went to lunch. He came back an hour later and the battery was completely dead. Either he got a lemon battery or something else is going on...

Opened Power Options control panel... Sure enough, the power profile was still set to "WOUTemp" even though the process completed successfully and the WOUTemp user was deleted after successfully running the client update. I set it back to Balanced and delete the WOUTemp profile, but that definitely should have been deleted automatically.

I used the UpdateInstaller.exe with C++, Silverlight, .NET 4.6.2, RDC, no verification, reboot and recall.