New
#1
Can someone please help me i have this exact problem here
Windows 7 update "Service Not Running Error" I really dont know what to do or how to fix this but its exactly the same
Windows 7 update "Service Not Running Error" I really dont know what to do or how to fix this but its exactly the same
Hi Brendan,
Have you run the troubleshooter, if not please do so.
Next lets have a look at a couple of logs
after running this from an elevated command mode
sfc /scannow (note the space)
post the the log from here
C >> Windows >> logs >> cbs >> cbs TEXT Document.
(zip it and attach)
and this tool, copy/paste the output
http://go.microsoft.com/fwlink/?LinkID=52012
Been hit by malware recently??
Roy
How to reset Windows Update components
- Important
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
To reset the Windows Update components, follow these steps:
- Open a command prompt. To do this, use one of the following methods, depending on your version of Windows:
- Windows 10: Press and hold (or right-click) the Windows logo button on the taskbar and then select Command Prompt (Admin). Select Yes when the User Account Control box appears.
- Windows8.1 and Windows 8: From the Start screen, swipe in from the right side to display the charms, select Search, and then search for cmd. (Or, if you are using a keyboard and mouse, type cmd at the Start screen.) In the search results, press-and-hold or right-click Command Prompt, and then select Run as Administrator.
- Windows 7 and earlier versions: Press the Windows logo key + R, type cmd in the Run box, and then press Enter. Right-click cmd, and then select Run as Administrator.
- Stop the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
- net stop bits
- net stop wuauserv
- net stop appidsvc
- net stop cryptsvc
- Delete the qmgr*.dat files. To do this, at a command prompt, type the following command, and then press Enter: Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
- If this is your first attempt at resolving your Windows Update issues by following the steps in this article, you should skip step 4 and go to step 5. You should follow step 4 at this point in the troubleshooting only if you cannot resolve your Windows Update issues after you follow all steps except step 4. (Step 4 is performed by the "Aggressive" mode of the Fix it Solution that was mentioned earlier.)
- Rename the softare distribution folders backup copies. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
- Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
- Ren %systemroot%\system32\catroot2 catroot2.bak
- Reset the BITS service and the Windows Update service to the default security descriptor. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
- sc.exe sdset bits DA;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPD TLOCRRC;;;PU)
- sc.exe sdset wuauserv DA;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPD TLOCRRC;;;PU)
- At a command prompt, type the following command, and then press Enter: cd /d %windir%\system32
- Reregister the BITS files and the Windows Update files. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
- regsvr32.exe atl.dll
- regsvr32.exe urlmon.dll
- regsvr32.exe mshtml.dll
- regsvr32.exe shdocvw.dll
- regsvr32.exe browseui.dll
- regsvr32.exe jscript.dll
- regsvr32.exe vbscript.dll
- regsvr32.exe scrrun.dll
- regsvr32.exe msxml.dll
- regsvr32.exe msxml3.dll
- regsvr32.exe msxml6.dll
- regsvr32.exe actxprxy.dll
- regsvr32.exe softpub.dll
- regsvr32.exe wintrust.dll
- regsvr32.exe dssenh.dll
- regsvr32.exe rsaenh.dll
- regsvr32.exe gpkcsp.dll
- regsvr32.exe sccbase.dll
- regsvr32.exe slbcsp.dll
- regsvr32.exe cryptdlg.dll
- regsvr32.exe oleaut32.dll
- regsvr32.exe ole32.dll
- regsvr32.exe shell32.dll
- regsvr32.exe initpki.dll
- regsvr32.exe wuapi.dll
- regsvr32.exe wuaueng.dll
- regsvr32.exe wuaueng1.dll
- regsvr32.exe wucltui.dll
- regsvr32.exe wups.dll
- regsvr32.exe wups2.dll
- regsvr32.exe wuweb.dll
- regsvr32.exe qmgr.dll
- regsvr32.exe qmgrprxy.dll
- regsvr32.exe wucltux.dll
- regsvr32.exe muweb.dll
- regsvr32.exe wuwebv.dll
- Reset Winsock. To do this, at a command prompt, type the following command, and then press Enter: netsh winsock reset
- If you are running Windows XP, you have to configure the proxy settings. To do this, at a command prompt, type the following command, and then press Enter:
proxycfg.exe -d
If you are running other versions of Windows, at a command prompt, type the following command, and then press Enter: netsh winhttp reset proxy- Restart the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
- net start bits
- net start wuauserv
- net start appidsvc
- net start cryptsvc
- Windows Vista only: Clear the BITS queue. To do this, at a command prompt, type the following command, and then press Enter: bitsadmin.exe /reset /allusers
- Install the latest Windows Update Agent.
- Restart the computer.
NO REGISTRY CHANGES ARE REQUIRED AT THIS POINT @johncorosz SLEDGEHAMMERS are BAD news
AND CERTAINLY NOT ALL OF THE ABOVE
The Troubleshooter/reports i referred to and earlier will/should identify the root cause
Roy
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-WJ2H8-R6B6D-7QJB7
Windows Product Key Hash: ckKNc+BBPDWmo1LUlOkraNjlQ34=
Windows Product ID: 00359-OEM-8992687-00006
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {49F319A3-BBB6-4C7E-A633-AA6406FFB58D}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.150316-1654
TTS Error:
Validation Diagnostic:
Resolution Status: N/A
Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002
OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002
OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Opera\launcher.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed
File Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{49F319A3-BBB6-4C7E-A633-AA6406FFB58D}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-7QJB7</PKey><PID>00359-OEM-8992687-00006</PID><PIDType>2</PIDType><SID>S-1-5-21-954228593-4112342297-3879639238</SID><SYSTEM><Manufacturer>Acer</Manufacturer><Model>Aspire 5750Z</Model></SYSTEM><BIOS><Manufacturer>Acer</Manufacturer><Version>V1.12</Version><SMBIOSVersion major="2" minor="7"/><Date>20110711000000.000000+000</Date></BIOS><HWID>13923C07018400FE</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>ACRSYS</OEMID><OEMTableID>ACRPRDCT</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>
Spsys.log Content: 0x80070002
Licensing Data-->
Script execution time was exceeded on script "C:\Windows\system32\slmgr.vbs".
Script execution was terminated.
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: KgAAAAEAAQABAAEAAAABAAAAAQABAAEA6GEOxmyidgBY2GTj4tSQlS5z
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC ACRSYS ACRPRDCT
FACP ACRSYS ACRPRDCT
HPET ACRSYS ACRPRDCT
BOOT ACRSYS ACRPRDCT
MCFG ACRSYS ACRPRDCT
ASF! ACRSYS ACRPRDCT
SLIC ACRSYS ACRPRDCT
SSDT ACRSYS ACRPRDCT
ASPT ACRSYS ACRPRDCT
SSDT ACRSYS ACRPRDCT
SSDT ACRSYS ACRPRDCT
Hi Brendan,
from the tool
Licensing Data-->
Script execution time was exceeded on script "C:\Windows\system32\slmgr.vbs".
Script execution was terminated.
This error usually appears on a Domain linked computer!!
Thats the little devil causing the problem.
And this isnt helping things
Event Time Stamp: N/A
A little more info please,
Were you hit by malware, i did ask in my earlier post
Have you used and then removed Avast/Norton or McAfee
Both of the above cause this type of problem, so do registry editors used in tune-up type progs.
Right lets get round to fixing it
Please install KB971033
http://go.microsoft.com/fwlink/?linkid=152411
from an elevated command mode
slmgr /rilc
(follow any directions from it)
from a run command
regsvr32 vbscript.dll
REBOOT X2
Rerun the tool
Roy
note for me //t