Server 2012R2 stuck in OOBE, possibly the root cause of Windows Updates failing to install

Tim Palmer
Tim Palmer used Ask the Experts™
on
Hi techs,

I have a Windows Server 2012R2 system which is stuck in OOBE, and as such, is not receiving updates automatically.
I've been able to manually install windows updates using the steps in this article which allowed me to get 15 updates installed via Powershell, but the GUI method still fails.

The server was built in 2017, had WSUS offline patches applied to it, but hasn't been patching since

I've tried:
- sfc /scannow
- dism /online /cleanup-image /restorehealth
- dism /online /cleanup-image /restorehealth /source:z:\winsxs /limitaccess (to use another functioning windows system as the source)
- sysprep /oobe /reboot to get it out of sysprep
- manually update Windows Updates components (based on https://support.solarwindsmsp.com/kb/solarwinds_n-central/Microsoft-Windows-Update-Agent-Updates )
- registry changes to get it out of OOBE
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\ 
 IsOOBEInProgress  change to 0 from 1

Open in new window

- reset the Windows Update components by stopping BITS, Crypographic, Winodws update services and renaming c:\windows\softwaredistribution to .old
- cleared the contents of the c:\windows\system32\catroot2 folder
- waited 5 days for the progress bar to progress
- confirmed server is not misconfigured to use WSUS
- reset the proxy settings using netsh winhttp import proxy source=ie
- reset the WindowsUpdate.log file to be able to get some fresh data, source below:

2019-04-03	15:28:49:493	1240	2144	Misc	===========  Logging initialized (build: 7.9.9600.18756, tz: +1100)  ===========
2019-04-03	15:28:49:493	1240	2144	Misc	  = Process: C:\Windows\system32\svchost.exe
2019-04-03	15:28:49:493	1240	2144	Misc	  = Module: c:\windows\system32\wuaueng.dll
2019-04-03	15:28:49:493	1240	2144	Service	*************
2019-04-03	15:28:49:493	1240	2144	Service	** START **  Service: Service startup
2019-04-03	15:28:49:493	1240	2144	Service	*********
2019-04-03	15:28:49:509	1240	2144	IdleTmr	Non-AoAc machine.  Aoac operations will be ignored.
2019-04-03	15:28:49:509	1240	2144	Agent	  * WU client version 7.9.9600.18756
2019-04-03	15:28:49:509	1240	2144	Agent	WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2019-04-03	15:28:49:509	1240	2144	Agent	  * Base directory: C:\Windows\SoftwareDistribution
2019-04-03	15:28:49:509	1240	2144	Agent	  * Access type: No proxy
2019-04-03	15:28:49:509	1240	2144	Service	UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2019-04-03	15:28:49:509	1240	2144	Service	UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
2019-04-03	15:28:49:509	1240	2144	Agent	  * Network state: Connected
2019-04-03	15:28:49:509	1240	2144	Service	UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2019-04-03	15:28:49:509	1240	2144	Service	UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
2019-04-03	15:28:49:540	1240	2144	Agent	***********  Agent: Initializing global settings cache  ***********
2019-04-03	15:28:49:540	1240	2144	Agent	  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2019-04-03	15:28:49:540	1240	2144	Agent	  * WSUS server: <NULL>
2019-04-03	15:28:49:540	1240	2144	Agent	  * WSUS status server: <NULL>
2019-04-03	15:28:49:540	1240	2144	Agent	  * Target group: (Unassigned Computers)
2019-04-03	15:28:49:540	1240	2144	Agent	  * Windows Update access disabled: No
2019-04-03	15:28:49:540	1240	2144	Misc	[b]WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll[/b]
2019-04-03	15:28:49:618	1240	2144	WuTask	WuTaskManager delay initialize completed successfully..
2019-04-03	15:28:49:618	1240	2144	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-03 04:54:23, not idle-only, not network-only
2019-04-03	15:28:49:618	1240	2144	AU	    Timer: 143FB093-8AA1-4DBC-A582-8806F8F4C1F7, Expires 2019-04-05 04:24:24, not idle-only, not network-only
2019-04-03	15:28:49:618	1240	2144	AU	    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2019-04-04 04:24:23, not idle-only, not network-only
2019-04-03	15:28:49:618	1240	2144	AU	    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-04-04 04:24:23, not idle-only, not network-only
2019-04-03	15:28:49:618	1240	2144	Report	CWERReporter::Init succeeded
2019-04-03	15:28:49:618	1240	2144	Agent	***********  Agent: Initializing Windows Update Agent  ***********
2019-04-03	15:28:49:618	1240	2144	DnldMgr	Download manager restoring 0 downloads
2019-04-03	15:28:49:618	1240	2144	AU	###########  AU: Initializing Automatic Updates  ###########
2019-04-03	15:28:49:618	1240	2144	AU	AIR Mode is disabled
2019-04-03	15:28:49:618	1240	2144	AU	  # Approval type: Pre-download notify (User preference)
2019-04-03	15:28:49:618	1240	2144	AU	  # Will interact with non-admins (Non-admins are elevated (User preference))
2019-04-03	15:28:49:618	1240	2144	AU	WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
2019-04-03	15:28:49:618	1240	2144	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-03	15:28:49:665	1240	2144	AU	AU finished delayed initialization
2019-04-03	15:28:49:665	1240	2144	AU	OOBE is in progress, so cannot perform Accelerated Install
2019-04-03	15:28:49:665	1240	2144	AU	Currently AUX is enabled - so not show any WU Upgrade notifications.
2019-04-03	15:28:49:665	1240	2144	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-03	15:28:49:665	1240	2144	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-03	15:28:49:696	1240	2144	AU	Adding timer: 
2019-04-03	15:28:49:696	1240	2144	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-03 04:54:23, not idle-only, not network-only
2019-04-03	15:28:49:696	1240	bc8	DnldMgr	Asking handlers to reconcile their sandboxes
2019-04-03	15:30:04:727	1240	2b04	IdleTmr	Incremented idle timer priority operation counter to 1
2019-04-03	15:30:04:727	4588	1710	Misc	===========  Logging initialized (build: 7.9.9600.18756, tz: +1100)  ===========
2019-04-03	15:30:04:727	4588	1710	Misc	  = Process: C:\Windows\explorer.exe
2019-04-03	15:30:04:727	4588	1710	Misc	  = Module: C:\Windows\system32\wucltux.dll
2019-04-03	15:30:04:727	4588	1710	CltUI	FATAL: CNetworkCostChangeHandler::RegisterForCostChangeNotifications: CoCreateInstance failed with error 80004002
2019-04-03	15:30:04:727	4588	1710	CltUI	WARNING: RegisterNetworkCostChangeNotification: Error 80004002
2019-04-03	15:30:06:852	1240	1940	AU	Triggering AU detection through DetectNow API
2019-04-03	15:30:06:852	1240	1940	AU	Triggering Online detection (interactive)
2019-04-03	15:30:06:852	1240	1940	AU	Adding timer: 
2019-04-03	15:30:06:852	1240	1940	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-03 04:30:06, not idle-only, not network-only
2019-04-03	15:30:06:852	1240	2144	AU	[b]Windows OOBE is still in progress. AU deferring detection[/b]
2019-04-03	15:30:06:852	1240	2144	AU	WARNING: BeginDetection failed, hr:0x8024a008
2019-04-03	15:30:06:852	1240	2144	AU	All AU searches complete.
2019-04-03	15:30:06:852	1240	2144	AU	  # WARNING: Failed to find updates with error code 8024a008
2019-04-03	15:30:06:868	1240	2144	AU	AU setting next detection timeout to 2019-04-03 05:00:06
2019-04-03	15:30:06:868	1240	2144	AU	Adding timer: 
2019-04-03	15:30:06:868	1240	2144	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-03 05:00:06, not idle-only, not network-only
2019-04-03	15:30:06:868	1240	2144	AU	[b]OOBE is in progress, so cannot perform Accelerated Install[/b]
2019-04-03	15:30:06:868	1240	2144	AU	Currently AUX is enabled - so not show any WU Upgrade notifications.
2019-04-03	15:30:06:868	1240	2144	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-03	15:30:06:868	1240	2144	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037

Open in new window


Does anyone have any other suggestions?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2017

Commented:
Get and run, possibly several tines
https://support.microsoft.com/en-us/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness

Had an occasion for a workstation to run it three times to get windows update to work again.
Tim PalmerLevel 3 Support Technician

Author

Commented:
Thanks, I've tried a dism a couple of times, but I'll try it a few more times for good measure.
The second part isn't relevant as it pertains to Windows 7 and 2008.

I've also come across this article on my searches because the link is showing as visited (and I believe it's in the top 5 Google results)
Distinguished Expert 2017

Commented:
get the windows update tool and run it against your ..
Though do not recall if I had to do it with a windows server 2012.
Try using the windows update check against the ms servers versus your own WSUS ..

At times, the issue could be that an update approved corrupts the DB because another update was not approved...


See if the following link that makes a registry change that changes the status ......
https://dannymccaslin.wordpress.com/2015/09/25/oobe-problems-with-windows-server-2012r2-updates/
Learn Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

Tim PalmerLevel 3 Support Technician

Author

Commented:
Looks like I've visited this link before too :)

The client doesn't have WSUS and I've already installed the updates for Windows Update.

I'll try the registry change again and reboot overnight and see if that sticks this time.

I'm on my 3rd DISM and it allegedly fixes things, but I haven't had time to go through the dism.log yet.
Tim PalmerLevel 3 Support Technician

Author

Commented:
OK So I have tried the registry changes, as well as a reboot overnight but it's still erroring.
The latest WindowsUpdate.log appears pretty much the same as the others.

2019-04-16	07:57:34:472	1244	1868	Misc	===========  Logging initialized (build: 7.9.9600.19164, tz: +1000)  ===========
2019-04-16	07:57:34:472	1244	1868	Misc	  = Process: C:\Windows\system32\svchost.exe
2019-04-16	07:57:34:472	1244	1868	Misc	  = Module: c:\windows\system32\wuaueng.dll
2019-04-16	07:57:34:472	1244	1868	Service	*************
2019-04-16	07:57:34:472	1244	1868	Service	** START **  Service: Service startup
2019-04-16	07:57:34:472	1244	1868	Service	*********
2019-04-16	07:57:34:550	1244	1868	IdleTmr	Non-AoAc machine.  Aoac operations will be ignored.
2019-04-16	07:57:34:550	1244	1868	Agent	  * WU client version 7.9.9600.19164
2019-04-16	07:57:34:550	1244	1868	Agent	WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2019-04-16	07:57:34:550	1244	1868	Agent	  * Base directory: C:\Windows\SoftwareDistribution
2019-04-16	07:57:34:550	1244	1868	Agent	  * Access type: No proxy
2019-04-16	07:57:34:550	1244	1868	Service	UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2019-04-16	07:57:34:550	1244	1868	Service	UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2019-04-16	07:57:34:550	1244	1868	Agent	  * Network state: Connected
2019-04-16	07:57:34:566	1244	1868	Service	UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2019-04-16	07:57:34:566	1244	1868	Service	UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2019-04-16	07:57:34:597	1244	1868	Agent	***********  Agent: Initializing global settings cache  ***********
2019-04-16	07:57:34:597	1244	1868	Agent	  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2019-04-16	07:57:34:597	1244	1868	Agent	  * WSUS server: <NULL>
2019-04-16	07:57:34:597	1244	1868	Agent	  * WSUS status server: <NULL>
2019-04-16	07:57:34:597	1244	1868	Agent	  * Target group: (Unassigned Computers)
2019-04-16	07:57:34:597	1244	1868	Agent	  * Windows Update access disabled: No
2019-04-16	07:57:34:597	1244	1868	Misc	WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
2019-04-16	07:57:34:722	1244	1868	WuTask	WuTaskManager delay initialize completed successfully..
2019-04-16	07:57:34:722	1244	1868	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-15 18:02:54, not idle-only, not network-only
2019-04-16	07:57:34:722	1244	1868	AU	    Timer: 143FB093-8AA1-4DBC-A582-8806F8F4C1F7, Expires 2019-04-16 22:15:55, not idle-only, not network-only
2019-04-16	07:57:34:722	1244	1868	AU	    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2019-04-16 17:14:04, not idle-only, not network-only
2019-04-16	07:57:34:722	1244	1868	AU	    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-04-16 17:14:00, not idle-only, not network-only
2019-04-16	07:57:34:753	1244	1868	Report	CWERReporter::Init succeeded
2019-04-16	07:57:34:753	1244	1868	Agent	***********  Agent: Initializing Windows Update Agent  ***********
2019-04-16	07:57:34:753	1244	1868	DnldMgr	Download manager restoring 0 downloads
2019-04-16	07:57:34:753	1244	1868	AU	###########  AU: Initializing Automatic Updates  ###########
2019-04-16	07:57:34:753	1244	1868	AU	AU setting next detection timeout to 2019-04-15 21:57:34
2019-04-16	07:57:34:753	1244	1868	AU	AIR Mode is disabled
2019-04-16	07:57:34:753	1244	1868	AU	  # Approval type: Pre-download notify (User preference)
2019-04-16	07:57:34:753	1244	1868	AU	  # Will interact with non-admins (Non-admins are elevated (User preference))
2019-04-16	07:57:34:753	1244	1868	AU	WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
2019-04-16	07:57:34:753	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	07:57:34:800	1244	1868	AU	AU finished delayed initialization
2019-04-16	07:57:34:800	1244	1868	AU	OOBE is in progress, so cannot perform Accelerated Install
2019-04-16	07:57:34:800	1244	1868	AU	Currently AUX is enabled - so not show any WU Upgrade notifications.
2019-04-16	07:57:34:800	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	07:57:34:800	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	07:57:34:831	1244	1868	AU	Adding timer: 
2019-04-16	07:57:34:831	1244	1868	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-15 21:57:34, not idle-only, not network-only
2019-04-16	07:57:34:831	1244	11fc	DnldMgr	Asking handlers to reconcile their sandboxes
2019-04-16	07:57:34:831	1244	1868	AU	Windows OOBE is still in progress. AU deferring detection
2019-04-16	07:57:35:472	1244	1868	AU	WARNING: BeginDetection failed, hr:0x8024a008
2019-04-16	07:57:35:472	1244	1868	AU	All AU searches complete.
2019-04-16	07:57:35:472	1244	1868	AU	  # WARNING: Failed to find updates with error code 8024a008
2019-04-16	07:57:35:472	1244	1868	AU	AU setting next detection timeout to 2019-04-15 22:27:35
2019-04-16	07:57:35:472	1244	1868	AU	Adding timer: 
2019-04-16	07:57:35:472	1244	1868	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-15 22:27:35, not idle-only, not network-only
2019-04-16	07:57:35:472	1244	1868	AU	OOBE is in progress, so cannot perform Accelerated Install
2019-04-16	07:57:35:472	1244	1868	AU	Currently AUX is enabled - so not show any WU Upgrade notifications.
2019-04-16	07:57:35:472	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	07:57:35:472	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	08:00:58:628	1244	1bb0	IdleTmr	Incremented idle timer priority operation counter to 1
2019-04-16	08:00:58:628	7564	1d1c	Misc	===========  Logging initialized (build: 7.9.9600.18970, tz: +1000)  ===========
2019-04-16	08:00:58:628	7564	1d1c	Misc	  = Process: C:\Windows\Explorer.EXE
2019-04-16	08:00:58:628	7564	1d1c	Misc	  = Module: C:\Windows\system32\wucltux.dll
2019-04-16	08:00:58:628	7564	1d1c	CltUI	FATAL: CNetworkCostChangeHandler::RegisterForCostChangeNotifications: CoCreateInstance failed with error 80004002
2019-04-16	08:00:58:628	7564	1d1c	CltUI	WARNING: RegisterNetworkCostChangeNotification: Error 80004002
2019-04-16	08:01:00:456	1244	1bb0	AU	Triggering AU detection through DetectNow API
2019-04-16	08:01:00:456	1244	1bb0	AU	Triggering Online detection (interactive)
2019-04-16	08:01:00:456	1244	1bb0	AU	Adding timer: 
2019-04-16	08:01:00:456	1244	1bb0	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-15 22:01:00, not idle-only, not network-only
2019-04-16	08:01:00:456	1244	1868	AU	Windows OOBE is still in progress. AU deferring detection
2019-04-16	08:01:00:456	1244	1868	AU	WARNING: BeginDetection failed, hr:0x8024a008
2019-04-16	08:01:00:456	1244	1868	AU	All AU searches complete.
2019-04-16	08:01:00:456	1244	1868	AU	  # WARNING: Failed to find updates with error code 8024a008
2019-04-16	08:01:00:456	1244	1868	AU	AU setting next detection timeout to 2019-04-15 22:31:00
2019-04-16	08:01:00:456	1244	1868	AU	Adding timer: 
2019-04-16	08:01:00:456	1244	1868	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-15 22:31:00, not idle-only, not network-only
2019-04-16	08:01:00:456	1244	1868	AU	OOBE is in progress, so cannot perform Accelerated Install
2019-04-16	08:01:00:456	1244	1868	AU	Currently AUX is enabled - so not show any WU Upgrade notifications.
2019-04-16	08:01:00:456	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	08:01:00:472	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	08:31:00:500	1244	1868	AU	Windows OOBE is still in progress. AU deferring detection
2019-04-16	08:31:00:500	1244	1868	AU	WARNING: BeginDetection failed, hr:0x8024a008
2019-04-16	08:31:00:500	1244	1868	AU	All AU searches complete.
2019-04-16	08:31:00:500	1244	1868	AU	  # WARNING: Failed to find updates with error code 8024a008
2019-04-16	08:31:00:500	1244	1868	AU	AU setting next detection timeout to 2019-04-15 23:01:00
2019-04-16	08:31:00:500	1244	1868	AU	Adding timer: 
2019-04-16	08:31:00:500	1244	1868	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-15 23:01:00, not idle-only, not network-only
2019-04-16	08:31:00:500	1244	1868	AU	OOBE is in progress, so cannot perform Accelerated Install
2019-04-16	08:31:00:500	1244	1868	AU	Currently AUX is enabled - so not show any WU Upgrade notifications.
2019-04-16	08:31:00:500	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	08:31:00:500	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	09:01:00:519	1244	1868	AU	Windows OOBE is still in progress. AU deferring detection
2019-04-16	09:01:00:519	1244	1868	AU	WARNING: BeginDetection failed, hr:0x8024a008
2019-04-16	09:01:00:519	1244	1868	AU	All AU searches complete.
2019-04-16	09:01:00:519	1244	1868	AU	  # WARNING: Failed to find updates with error code 8024a008
2019-04-16	09:01:00:535	1244	1868	AU	AU setting next detection timeout to 2019-04-15 23:31:00
2019-04-16	09:01:00:535	1244	1868	AU	Adding timer: 
2019-04-16	09:01:00:535	1244	1868	AU	    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-04-15 23:31:00, not idle-only, not network-only
2019-04-16	09:01:00:535	1244	1868	AU	OOBE is in progress, so cannot perform Accelerated Install
2019-04-16	09:01:00:535	1244	1868	AU	Currently AUX is enabled - so not show any WU Upgrade notifications.
2019-04-16	09:01:00:535	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	09:01:00:535	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	09:14:20:090	1244	1868	AU	OOBE is in progress, so cannot perform Accelerated Install
2019-04-16	09:14:20:090	1244	1868	AU	Currently AUX is enabled - so not show any WU Upgrade notifications.
2019-04-16	09:14:20:105	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	09:14:20:121	1244	1868	AU	WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-04-16	09:14:20:152	1244	1868	AU	OOBE is in progress, so cannot perform Accelerated Install

Open in new window

Tim PalmerLevel 3 Support Technician

Author

Commented:
Anyone else have any ideas?
Hi Tim

Have you seen this?
https://dannymccaslin.wordpress.com/2015/09/25/oobe-problems-with-windows-server-2012r2-updates/

I had a similar problem in the past. After the steps you have already taken AND using powershell windows update tool, it was gone.
https://dannymccaslin.wordpress.com/2015/09/25/oobe-problems-with-windows-server-2012r2-updates/

I hope that will help you as well.

edit: https://gallery.technet.microsoft.com/scriptcenter/2d191bcd-3308-4edd-9de2-88dff796b0bc/

regards
Thomas
Tim PalmerLevel 3 Support Technician

Author

Commented:
Thanks for the suggestions guys, sorry for the delay I've been away for 5 weeks.
The updates still aren't working, and nothing suggested so far has been able to fix the server.

If anyone else has any suggestions I'll be open to hearing it!
I bet my pants it is exactly what I mentioned.

use the links to remove the registry entry.
After that download and "install" the powershell script and execute it.

I had the exact same error more than once and this helped all the time. I needs some patience after executing the powershell script. It does not work within a minute, just let it run...
Tim PalmerLevel 3 Support Technician

Author

Commented:
I'll give it another try if the client approves me another reboot, but be prepared to mail me your pants :P

In my initial post, I mentioned I had already tried
- registry changes to get it out of OOBE
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\
 IsOOBEInProgress  change to 0 from 1

Are you suggesting I change this key (using powershell as admin rather than regedit), and then the powershell, or is there a reboot inbetween?

I've had the powershell work for updating the machine, but that didn't fix the GUI.

To confirm, you're saying that the powershell reg change AND the powershell update script, fixed your GUI issue?
When I had gotten back from leave, after 5 weeks the GUI was still scrolling through checking!

Did you have to do any other steps than the above?
Hi Tim

The registry Key must be 0. you can change it with regedit.

Once you completely updated the machine with the powershell script (I would run it multiple times, reboot, run again)
the GUI should work again. At least I got it back to work.

Apart from getting my pants ripped of ;) I do not have more steps /advice to give you on this
Tim PalmerLevel 3 Support Technician

Author

Commented:
I think I may have written that wrong, but without my case notes I can't be sure, but yep, I'll make sure it's 0.

Thanks, I'll let you know hopefully soon
Level 3 Support Technician
Commented:
OK so to close this one off - I finally logged a case with Microsoft and they gave me 2 options.

Powershell to update, or rebuild the server.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial