Link to home
Start Free TrialLog in
Avatar of Hooznext
Hooznext

asked on

Windows Update keeps asking for a reboot

Windows Update on Server 2008 x64 with SP2 will continue to ask for a reboot every time I start the computer. I have ran Microsoft's fix it utility for resetting windows update but it continues to ask for a reboot. It displays the following message.

Windows can't update important files and services while the system is using them. Save any open files and restart the computer, and then try to check for new updates.

I have done this numerous time and get the same thing.

I've attached my Windows Update Log
Windows-Update-Log.txt
Avatar of Don
Don
Flag of United States of America image

"AU got client choice 'Reboot later' in 240 mins"

This means a user postponed the reboot

You say "...every time I start the computer"

Have you rebooted ???
Hello.
stop the windows updates service. it will stop asking for a reboot .
hope that helps
Stopping the service is only a bandaid, not a solution
Avatar of Hooznext
Hooznext

ASKER

I have postponed the reboot every time I log on. I have rebooted over 5 times and get the exact same issue. If I stop the service it does not fix the issue.

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.22574
Package Version 13.0
2011-12-09 13:25

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 457
 No errors detected


Try:

Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\PendingFileRenameOperations    

Back up the registry key
Delete the registry key
I do not have that registry key.
hmmm...that's the key that controls whether a reboot is needed



check(regardless if you have exchange or not)


http://technet.microsoft.com/en-us/library/cc164360%28EXCHG.80%29.aspx
Don't have that either. The only key I have that is close to that is FileRenameOperations.
I've opened a support case with Microsoft and they can't seem to figure it out and are involving their security team. I believe it has to be a registry back that was exported before installing three drivers and imported after the drivers where installed.
I've requested that this question be closed as follows:

Accepted answer: 0 points for Hooznext's comment #a37264837

for the following reason:

Had to have Microsoft engineers fix it.
"Had to have Microsoft engineers fix it."  ???


What did they do ???
ASKER CERTIFIED SOLUTION
Avatar of Hooznext
Hooznext

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Opened case with Microsoft to resolve the issue.