Share via


ScheduledInstallTime registry key is not applied

Question

Wednesday, May 21, 2014 2:54 PM

Hello everyone

I am struggling to understand why my windows 7 machine although it downloads the updates from the server (2008 R2), it does not install them.

The windows 7 PC is not a domain member, is a stand-alone machine and I manually created the registry keys using this KB:http://support.microsoft.com/kb/328010

Here are my registry keys in HLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU:

  • AUOptions=0x00000004(4)
  • NoAutoRebootWithLoggedOnUsers=0x00000001(1)
  • NoAutoUpdate=0x00000000(0)
  • ScheduledInstalledDay=0x00000000(0)
  • ScheduledInstallTime=0x00000016(22) (16 is equal to 16:00pm right?)
  • UseWUServer= 0x00000001(1)

Here are my registry keys in HLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate:

  • WUServer=http://server
  • WUStatusServer=http://server

However the updates does not get installed. I have changed the ScheduledInstallTime key value several times but it does not get applied. The PC is downloading the updates but they don't get installed.

Could you please let me if i am doing something wrong or have missed something.

Many thanks

All replies (7)

Thursday, May 22, 2014 4:18 PM ✅Answered

Thanks Armin

My ScheduledInstallTime value was indeed wrong. I have now changed that and updates kick-in the correct time.

At the same time, I was googling to find out how to locate the port that WSUS is using and I found out that you can see that through the IIS console. Then after spending like an hour looking for it (IIS), I realised that is not actually installed, so I installed it and I can confirm that http is bind to port 80.

During that time I corrected the  ScheduledInstallTime value and updates worked fine. That was before I install IIS. So my question is: Do I really have to change the default http port to 8530?

In case someone else needs it, here are the hex values and their equivalent times for ScheduledInstallTime :

0x00000000 midnight
0x00000001- 1am
0x00000002- 2am
0x00000003- 3am
0x00000004- 4am
0x00000005- 5am
0x00000006- 6am
0x00000007- 7am
0x00000008- 8am
0x00000009- 9am
0x0000000A- 10am
0x0000000B- 11am
0x0000000C- 12am
0x0000000D- 1pm
0x0000000E- 2pm
0x0000000F- 3pm
0x00000010- 4pm
0x00000011- 5pm
0x00000012- 6pm
0x00000013- 7pm
0x00000014- 8pm
0x00000015- 9pm
0x00000016- 10pm
0x00000017- 11pm

Thursday, May 22, 2014 4:56 PM ✅Answered

no IIS or just no IIS console? it needs IIS to function so that's kind of odd if it wasn't actually installed

it's just recommended to have it run on something other than 80 that's all, it's fine if you already have it on 80 and know that on that server you won't have another web application will need 80 later on

in 2012 when you install WSUS it puts the port on 8530/8531 by default but in the old versions it just uses 80 unless you specify otherwise, sounds like you're up and running now.


Wednesday, May 21, 2014 5:57 PM | 1 vote

do you know if it's attempted to install the updates and failed or it's not attempting at all?

you should verify the GPOs by running rsop.msc, ensure you have done either gpupdate /force or rebooted the workstation to push the settings down

check the WU log and see what's happening after the scheduled time when the updates should be getting pushed: C:\windows\windowsupdate.log

I'm sure event viewer will have some indications as well

how do you know the updates are in fact downloading?

make sure your C drive has sufficient free disk space as well

finally, you can stop the Windows Update service, delete C:\windows\SoftwareDistribution, reboot and see if it help


Thursday, May 22, 2014 5:59 AM | 1 vote

Hi,

Since this computer is not joined domain, I guess it is not configured via GPO.

Also WSUS is usually installed on port 8530, you should set the two registry key like:

WUServer=http://server:8530

WUStatusServer=http://server:8530

At last, as armin19 mentioned, windowsupdate.log may help address the issue.

Hope this helps.


Thursday, May 22, 2014 9:20 AM

Like Daniel said, my WSUS is not configured via GPO because this PC does not belong to any domain. I manually created the registry keys to download and install updates from the server.

If I do: wuauclt.exe /detectnow the PC is checking for updates and is telling me the number of updates available. Also in the Windows Update window under "You receive updates", it says: Managed by your system administrator.

Anyway, yesterday when I left the PC there were 3 updates available and I set the "ScheduledInstallTime=0x00000017(23)", (PC rebooted after registry change) which I thought it will install the updates at 17:00pm but this morning, I checked the WindowsUpdate.log file and I can see the following (file too big so I pasted it here):

http://pastebin.com/aqUxwMzS

Please see the file in the above link, I've pasted only the log after the 17:00. You will notice that at 17:00pm which is the time set to install the updates, there are only 2 lines:

2014-05-21 16:59:30:940  1056 1474 AU Launched new AU client for directive 'Install Approval', session id= 0x2
2014-05-21  17:00:08:449    1056    b10   AU    Getting featured update notifications.  fIncludeDismissed = true
2014-05-21  17:00:08:449    1056    b10    AU    No featured updates available.
2014-05-21  23:00:10:003    1056    1474    AU    Forced install timer expired for scheduled install
2014-05-21  23:00:10:003  1056    1474    AU    UpdateDownloadProperties: 0 download(s) are still in progress.
2014-05-21  23:00:10:003    1056    1474    AU    #############
2014-05-21  23:00:10:003    1056    1474    AU    ## START ##  AU: Install updates
2014-05-21  23:00:10:003    1056    1474    AU    #########
2014-05-21  23:00:10:003    1056    1474    AU      # Initiating scheduled install
2014-05-21  23:00:10:003    1056    1474    AU      # Approved updates = 3                                         2014-05-21  23:00:10:050    1056    1474    AU    <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {5D819936-7EBA-4C9C-A951-71A624FDFB4A}]
2014-05-21    23:00:10:050    1056    16f4    Agent    *************
2014-05-21 23:00:10:050 1056  16f4 Agent   **START** Agent: Installing updates [CallerId = AutomaticUpdates]
2014-05-21    23:00:10:050    1056    16f4    Agent    *********
2014-05-21    23:00:10:050    1056    16f4    Agent      * Updates to install = 3

So the updates did get installed but at 23:00 instead of 17:00pm.

Is my "ScheduledInstallTime" wrong??? Any suggestions please?

Many thanks


Thursday, May 22, 2014 10:43 AM

I did a netstat -a and port 8530 is not listed. Should I set the registry keys as you suggested anyway?


Thursday, May 22, 2014 1:17 PM | 1 vote

"ScheduledInstallTime=0x00000017(23)" is not correct for 5PM, you put 17 in the Hex box, you need to put 17 in the Decimal box instead, that's why it was patched at 11PM

I'm also not certain if your WSUS is actually setup on port 8530, it's clearly providing updates and the client is getting it, looking at your log there is no reference to 8530:

http://testserver1/ReportingWebService/ReportingWebService.asmx

it would be http://testserver1:8530/ReportingWebService/ReportingWebService.asmx if it was setup that way

so you need to first identify from the WSUS console if you are in fact setup on 8530 as it appears you're setup on port 80 instead (the default)

you're also using NoAutoRebootWithLoggedOnUsers=0x00000001(1) - if anyone is logged in it won't reboot as planned, so make sure no one is on the PCs when you're testing this or get rid of the key