[SOLVED] Windows Update is promting me to reboot

G

gpeters

Member
Joined
Apr 11, 2015
Posts
18
My notebook is prompting me to reboot from a windows update but it is all uptodate. On the Windows Update screen it shows "Windows is up to date" but I still get the reboot prompt and can dismiss it for 4 hour and it comes back agian. No matter how many time I reboot it keeps on coming back.

I ran the SFCFix and it did not find/fix any issues

The CSB zip file is 23MB...too large to upload here. How can I post it here?
 

Attachments

Yes it is prompting me now. There are no updates to install. It says "Windows is up to date"
 
OK, please do the following. When you are prompted to reboot go ahead and then immediately do the following.

Step#1 - Retrieve Event Log Messages
1. Download Event Viewer Tool by Vino Rosso to your Desktop
2. Right-click on the file (VEW.exe) and select Run as administrator.
3. Check the options as shown below and put 20 in for the number of events.
4. Click Run. After a few moments, notepad will open with the contents of the Event Logs. Please copy and paste these in your next post. Thank you.

Capture.JPG
 
Here are the results as per your request

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 19/04/2015 1:32:13 PM


Note: All dates below are in the format dd/mm/yyyy


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/04/2015 5:02:29 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\plugin\File\explorers\freecommander\files\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\plugin\File\explorers\freecommander\files\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 19/04/2015 5:01:43 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\plugin\antispyware\Spybot\files\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\plugin\antispyware\Spybot\files\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 19/04/2015 5:01:08 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\BartPE\PROGRAMS\spybot\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\BartPE\PROGRAMS\spybot\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 19/04/2015 4:57:58 AM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.


Log: 'Application' Date/Time: 19/04/2015 4:57:36 AM
Type: Error Category: 0
Event: 9 Source: SideBySide
Activation context generation failed for "C:\Users\gerhard.IVERSA\AppData\Roaming\salesforce.com\Salesforce for Outlook\adxloader.dll.Manifest".Error in manifest or policy file "C:\Users\gerhard.IVERSA\AppData\Roaming\salesforce.com\Salesforce for Outlook\adxloader.dll.Manifest" on line 2. The manifest file root element must be assembly.


Log: 'Application' Date/Time: 18/04/2015 4:32:34 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\plugin\File\explorers\freecommander\files\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\plugin\File\explorers\freecommander\files\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 18/04/2015 4:31:27 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\plugin\antispyware\Spybot\files\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\plugin\antispyware\Spybot\files\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 18/04/2015 4:30:49 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\BartPE\PROGRAMS\spybot\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\BartPE\PROGRAMS\spybot\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 18/04/2015 4:27:05 AM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.


Log: 'Application' Date/Time: 18/04/2015 4:26:24 AM
Type: Error Category: 0
Event: 9 Source: SideBySide
Activation context generation failed for "C:\Users\gerhard.IVERSA\AppData\Roaming\salesforce.com\Salesforce for Outlook\adxloader.dll.Manifest".Error in manifest or policy file "C:\Users\gerhard.IVERSA\AppData\Roaming\salesforce.com\Salesforce for Outlook\adxloader.dll.Manifest" on line 2. The manifest file root element must be assembly.


Log: 'Application' Date/Time: 17/04/2015 5:46:30 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\plugin\File\explorers\freecommander\files\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\plugin\File\explorers\freecommander\files\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 17/04/2015 5:45:45 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\plugin\antispyware\Spybot\files\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\plugin\antispyware\Spybot\files\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 17/04/2015 5:45:10 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\BartPE\PROGRAMS\spybot\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\BartPE\PROGRAMS\spybot\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 17/04/2015 5:42:05 AM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.


Log: 'Application' Date/Time: 17/04/2015 5:41:47 AM
Type: Error Category: 0
Event: 9 Source: SideBySide
Activation context generation failed for "C:\Users\gerhard.IVERSA\AppData\Roaming\salesforce.com\Salesforce for Outlook\adxloader.dll.Manifest".Error in manifest or policy file "C:\Users\gerhard.IVERSA\AppData\Roaming\salesforce.com\Salesforce for Outlook\adxloader.dll.Manifest" on line 2. The manifest file root element must be assembly.


Log: 'Application' Date/Time: 16/04/2015 3:17:47 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\plugin\File\explorers\freecommander\files\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\plugin\File\explorers\freecommander\files\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 16/04/2015 3:16:43 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\plugin\antispyware\Spybot\files\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\plugin\antispyware\Spybot\files\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 16/04/2015 3:15:56 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\UBCD4Win\BartPE\PROGRAMS\spybot\DelZip179.dll".Error in manifest or policy file "c:\UBCD4Win\BartPE\PROGRAMS\spybot\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.


Log: 'Application' Date/Time: 16/04/2015 3:10:28 PM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.


Log: 'Application' Date/Time: 16/04/2015 3:09:33 PM
Type: Error Category: 0
Event: 9 Source: SideBySide
Activation context generation failed for "C:\Users\gerhard.IVERSA\AppData\Roaming\salesforce.com\Salesforce for Outlook\adxloader.dll.Manifest".Error in manifest or policy file "C:\Users\gerhard.IVERSA\AppData\Roaming\salesforce.com\Salesforce for Outlook\adxloader.dll.Manifest" on line 2. The manifest file root element must be assembly.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 15/04/2015 3:50:30 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Visio 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\TypeLib.


Log: 'Application' Date/Time: 15/04/2015 3:50:30 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Visio 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\TypeLib.


Log: 'Application' Date/Time: 15/04/2015 3:50:30 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Visio 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\ProxyStubClsid32.


Log: 'Application' Date/Time: 15/04/2015 3:50:30 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Visio 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\ProxyStubClsid.


Log: 'Application' Date/Time: 15/04/2015 3:50:30 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Visio 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}.


Log: 'Application' Date/Time: 15/04/2015 3:50:21 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Professional Plus 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\TypeLib.


Log: 'Application' Date/Time: 15/04/2015 3:50:21 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Professional Plus 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\TypeLib.


Log: 'Application' Date/Time: 15/04/2015 3:50:21 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Professional Plus 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\ProxyStubClsid32.


Log: 'Application' Date/Time: 15/04/2015 3:50:21 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Professional Plus 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\ProxyStubClsid.


Log: 'Application' Date/Time: 15/04/2015 3:50:21 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Professional Plus 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}.


Log: 'Application' Date/Time: 15/04/2015 3:38:07 PM
Type: Warning Category: 0
Event: 36 Source: Outlook
Search cannot complete the indexing of your Outlook data. Indexing cannot continue for C:\Users\gerhard.IVERSA\AppData\Local\Microsoft\Outlook\gerhard.peters@iversa.ca - Exchange.ost (error=0x809706ba). If this error continues, contact Microsoft Support.


Log: 'Application' Date/Time: 15/04/2015 3:36:32 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Visio 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\TypeLib.


Log: 'Application' Date/Time: 15/04/2015 3:36:32 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Visio 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\TypeLib.


Log: 'Application' Date/Time: 15/04/2015 3:36:32 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Visio 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\ProxyStubClsid32.


Log: 'Application' Date/Time: 15/04/2015 3:36:32 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Visio 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\ProxyStubClsid.


Log: 'Application' Date/Time: 15/04/2015 3:36:32 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Visio 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}.


Log: 'Application' Date/Time: 15/04/2015 3:36:23 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Professional Plus 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\TypeLib.


Log: 'Application' Date/Time: 15/04/2015 3:36:23 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Professional Plus 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\TypeLib.


Log: 'Application' Date/Time: 15/04/2015 3:36:23 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Professional Plus 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\ProxyStubClsid32.


Log: 'Application' Date/Time: 15/04/2015 3:36:23 PM
Type: Warning Category: 0
Event: 1039 Source: MsiInstaller
Product: Microsoft Office Professional Plus 2010. The application tried to modify a protected Windows registry key \Software\Classes\Interface\{BEF6E003-A874-101A-8BBA-00AA00300CAB}\ProxyStubClsid.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 17/04/2015 2:34:21 PM
Type: Error Category: 0
Event: 1 Source: VDS Basic Provider
Unexpected failure. Error code: 490@01010004


Log: 'System' Date/Time: 11/04/2015 6:00:57 PM
Type: Error Category: 0
Event: 3002 Source: Microsoft Antimalware
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed. Feature: Behavior Monitoring Error Code: 0x80004005 Error description: Unspecified error Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.


Log: 'System' Date/Time: 11/04/2015 6:00:15 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The MSCamSvc service failed to start due to the following error: The system cannot find the file specified.


Log: 'System' Date/Time: 11/04/2015 1:38:32 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80242016: Update for Windows 7 for x64-based Systems (KB2952664).


Log: 'System' Date/Time: 11/04/2015 1:38:10 AM
Type: Error Category: 0
Event: 3002 Source: Microsoft Antimalware
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed. Feature: Behavior Monitoring Error Code: 0x80004005 Error description: Unspecified error Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.


Log: 'System' Date/Time: 11/04/2015 1:37:20 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The MSCamSvc service failed to start due to the following error: The system cannot find the file specified.


Log: 'System' Date/Time: 21/03/2015 1:10:54 AM
Type: Error Category: 0
Event: 3002 Source: Microsoft Antimalware
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed. Feature: Behavior Monitoring Error Code: 0x80004005 Error description: Unspecified error Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.


Log: 'System' Date/Time: 21/03/2015 1:10:05 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The MSCamSvc service failed to start due to the following error: The system cannot find the file specified.


Log: 'System' Date/Time: 21/03/2015 1:06:42 AM
Type: Error Category: 0
Event: 3002 Source: Microsoft Antimalware
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed. Feature: Behavior Monitoring Error Code: 0x80004005 Error description: Unspecified error Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.


Log: 'System' Date/Time: 21/03/2015 1:05:46 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The MSCamSvc service failed to start due to the following error: The system cannot find the file specified.


Log: 'System' Date/Time: 21/03/2015 1:02:30 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout.


Log: 'System' Date/Time: 20/03/2015 3:41:09 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80240020: nVidia - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3, Other hardware - NVIDIA GeForce 9500 GT.


Log: 'System' Date/Time: 20/03/2015 3:30:14 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The uvnc_service service terminated unexpectedly. It has done this 1 time(s).


Log: 'System' Date/Time: 19/03/2015 3:42:06 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80240020: nVidia - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3, Other hardware - NVIDIA GeForce 9500 GT.


Log: 'System' Date/Time: 18/03/2015 2:15:29 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80240020: nVidia - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3, Other hardware - NVIDIA GeForce 9500 GT.


Log: 'System' Date/Time: 17/03/2015 2:43:54 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80240020: nVidia - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3, Other hardware - NVIDIA GeForce 9500 GT.


Log: 'System' Date/Time: 16/03/2015 2:54:17 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80240020: nVidia - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3, Other hardware - NVIDIA GeForce 9500 GT.


Log: 'System' Date/Time: 15/03/2015 10:11:28 PM
Type: Error Category: 0
Event: 3002 Source: Microsoft Antimalware
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed. Feature: Behavior Monitoring Error Code: 0x80004005 Error description: Unspecified error Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.


Log: 'System' Date/Time: 15/03/2015 10:10:31 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The MSCamSvc service failed to start due to the following error: The system cannot find the file specified.


Log: 'System' Date/Time: 15/03/2015 10:09:33 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The NVIDIA Stereoscopic 3D Driver Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 15/04/2015 2:01:07 AM
Type: Warning Category: 0
Event: 50 Source: Microsoft-Windows-Time-Service
The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.


Log: 'System' Date/Time: 08/04/2015 6:19:44 PM
Type: Warning Category: 0
Event: 50 Source: Microsoft-Windows-Time-Service
The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.


Log: 'System' Date/Time: 08/04/2015 1:25:51 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name iversa.ca timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 02/04/2015 3:54:21 AM
Type: Warning Category: 0
Event: 50 Source: Microsoft-Windows-Time-Service
The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.


Log: 'System' Date/Time: 01/04/2015 7:47:56 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ensayoes.com timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 23/03/2015 11:33:05 PM
Type: Warning Category: 0
Event: 50 Source: Microsoft-Windows-Time-Service
The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.


Log: 'System' Date/Time: 19/03/2015 8:25:22 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name partners.sagenorthamerica.com timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 19/03/2015 7:51:59 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name importel.webhop.org timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 19/03/2015 12:57:38 AM
Type: Warning Category: 0
Event: 50 Source: Microsoft-Windows-Time-Service
The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.


Log: 'System' Date/Time: 18/03/2015 9:41:20 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name s151095.trixbox.fonality.com timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 16/03/2015 6:50:30 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.desktoplinux.com timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 12/03/2015 5:19:47 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name lastpass.com timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 09/03/2015 3:45:58 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.nieonline.ca timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 04/03/2015 2:28:24 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name outlook.office365.com timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 04/03/2015 2:25:08 AM
Type: Warning Category: 0
Event: 27 Source: e1kexpress
Intel(R) 82578DC Gigabit Network Connection Network link is disconnected.


Log: 'System' Date/Time: 04/03/2015 12:14:55 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name 20.145.168.192.in-addr.arpa timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 04/03/2015 12:14:46 AM
Type: Warning Category: 0
Event: 131 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a domain peer to use as a time source because of DNS resolution error on ''. NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter. The error was: The requested name is valid, but no data of the requested type was found. (0x80072AFC).


Log: 'System' Date/Time: 04/03/2015 12:14:40 AM
Type: Warning Category: 0
Event: 27 Source: e1kexpress
Intel(R) 82578DC Gigabit Network Connection Network link is disconnected.


Log: 'System' Date/Time: 03/03/2015 10:55:52 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name dns.msftncsi.com timed out after none of the configured DNS servers responded.


Log: 'System' Date/Time: 03/03/2015 10:51:50 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name isatap.iversa.local timed out after none of the configured DNS servers responded.
 
Thanks for the info. Please follow the instructions below.

To summarize what you will be doing...

  1. Click the Start button
    4f6cbd09-148c-4dd8-b1f2-48f232a2fd33_818.jpg
    , type Run in the search box, and then, in the results list, click Run.
  2. Copy the following text, and then paste it into the Run text box:
    Cmd /c ren %systemroot%\System32\Spupdsvc.exe Spupdsvc.old
  3. Click OK.
  4. Try running windows updates again and see if anything shows up. If it does, install and reboot.

Info was obtained from the following article.

Windows Update error 8024000B - Windows Help
 
Finally had time to try it and that did not fix the problem. Still dealing with the annoying boot reminder. Still in reboot lock.
 
Also, please do the following.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please post the contents of the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
 
OK, please do the following and let's take a deeper look.

Please navigate to C:\Windows\winsxs and copy any files with a similar name to pending.xml (e.g. pending.xml, pending.xml.bad, pending.xml_dfsadf78 etc.) to your folder on the Desktop [there may not be any, just if there are]. Then zip up this folder and attach it to your next post.


  1. Click on the
    Win7Orb_zps4dae3b32.jpg
    button. Inside the search box type in CMD
  2. Right click on CMD => Choose Run as Administrator
  3. Inside the Command Prompt windows copy and paste the following command
    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
    REG QUERY HKLM\COMPONENTS >1&& notepad 1
  4. Please wait for this to Finish before continuing with rest of the steps.

Please also export the following registry keys, add them into a zip and attach to this post:


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\

  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file Update (with no file extension) and save it to your Desktop.


Once done please upload this file via Dropbox or One Drive or SendSpace.
 
OK, I see the issue now. We will try reverting the pending changes using built-in Windows tools. If this doesn't work we'll do it manually.

Boot into the Windows RE mode: How to use the Windows 7 System Recovery Environment Command Prompt

Once the command Window is displayed please follow the below steps.

First command to enter is wmic logicaldisk get name. you will be given a similar output to:

Code:
X:\Sources>wmic logicaldisk get name
Name
C:
D:
E:
X:
Now when you are in the RE the drive letters will often move around. start with the first letter that was provided in the list and enter in the following command (for this example we will use C:\ as it is the first one)

dir C:\
-This will display all the folders in the root drive of C

Can you see a folder called C:\Windows in list?
-If you can see C:\Windows then run the DISM command as DISM /Image:C:\ /Cleanup-Image /RevertPendingActions

If you can not see the Windows folder move onto the next Drive letter that we obtained with wmic logicaldisk get name and type in dir <DRIVE LETTER> (replace <DRIVE LETTER> with the drive you would like to check), can you see the Windows Folder?
-If yes, enter in the following command DISM /Image:C:\ /Cleanup-Image /RevertPendingActions and changed the C to what ever Drive letter has the Windows folder

Its just a case of going through each drive letter that was produced from the first list until the Windows folder is found then run the DISM command on that drive.

If you are prompted for a Scratch Directory please run the following:
mkdir C:\Scratch
DISM /Image:C:\ /ScratchDir:C:\Scratch /Cleanup-Image /RevertPendingActions
-Remember the drive letter in red needs to be changed like before.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top