Windows Update Troubleshooter v1.2
Product By:
Ashfaq Ansari
Version:
1.2
Price:
Free

Reviewed by:
Rating:
5
On April 13, 2011
Last modified:April 1, 2015

Summary:

Awesome VB script to fix issues related to Windows Update in Windows XP, Vista, and Windows 7. Automation of general Windows Update Troubleshooting steps.

Introduction

 

Windows Update help the users to keep their Computer up to date by downloading and installing Windows Updates that are released by Microsoft on a regular basis. Windows Update is a automated process that requires very less user interaction.
 

But the common users face a lot of issues with Windows Update. Windows Update encounters many types of errors that might be client side or server side.
 

 

To help such users HackSys Team presents a script that will try to fix some of the issues. Error occurs due to many reasons that are impossible to incorporate in a VBS script. So this script does the common Windows Update troubleshooting steps.
 

Download Link:
 

Windows_Update_Troublesho ..
 

New Version: Windows Update Troubleshooter v1.3
 

Windows_Update_Troublesho ..
 

Prototype of Widows Update Troubleshooter v1.2:
 

1. Disables User Account Control (UAC)

2. Creates a folder on Desktop named “Logs

3. Copies Windows Update Log file from C:\\WINDOWS\\windowsupdate.log to “Logs” folder on Desktop.

4. Stops Background Intelligent Transfer Service (BITS)

5. Stops Cryptographic Services (CryptSvc)

6. Stops Windows Update Service (wuauserv)

7. Renames SoftwareDistribution folder located at C:\\WINDOWS\\SoftwareDistribution

8. Renames CatRoot2 folder located at C:\\WINDOWS\\system32\\Catroot2

9. Starts Background Intelligent Transfer Service (BITS)

10. Starts Cryptographic Services (CryptSvc)

11. Starts Windows Update Service (wuauserv)

12. Launches System File Checker Scan (SFC)

13. Copies SFC Scan Log file C:\\WINDOWS\\Logs\\CBS\\CBS.log to “Logs” folder on Desktop

14. Launches Microsoft Fixit (Windows Update Component Reset)

15. Adds Microsoft Windows Update Sites to Internet Explorer Trust List

16. Launches System Update Readiness Tool (CheckSur)

17. Copying CheckSur Log file C:\\WINDOWS\\Logs\\CBS\\Checksur.log to “Logs” folder

18. Launching MSCONFIG (Microsoft Configuration Utility) for clean boot (All Startup Items and Non-Microsoft Services disabled)
 

Please try this script and leave the feed backs and you may request features. I will try to update the script as soon as possible.
 


 
 

212,156 total views, 55 views today

The following two tabs change content below.

Ashfaq Ansari

Security Researcher
Ashfaq Ansari is the founder of HackSys Team code named "Panthera". He is a Security Researcher with experience in various aspects of Information Security. He has authored "HackSys Extreme Vulnerable Driver" and "Shellcode of Death". He has also written and published various whitepapers on low level software exploitation. His core interest lies in "Low Level Exploitation", "Reverse Engineering", "Program Analysis" and "Hybrid Fuzzing". He is a fanboy of Artificial Intelligence and Machine Learning. He is the chapter lead for null Pune.

Latest posts by Ashfaq Ansari (see all)

71 Responses to “Windows Update Troubleshooter v1.2”

  1. Mark Kubesch says:

    HackSys Team,

    A great big thank you, kudos, props, etc. Version 1.3 fixed the 80248009 error on my windows 7 64 bit machine.

    Mark

  2. HackSys Team/Pantera,

    I do not have the download link for the Windows 7, and the computer in question is a 32 bit.

    /r
    Jimsan

  3. Hacksys Team,

    Following steps in provided link;

    Install the latest version of CheckSUR.

    Workaround 1: Follow the steps from Phyxion on properly restoring the drivers: http://forum.phyxion.net/viewtopic.php?id=17

    (This is not an issue because did not do any diver cleaning).
    _______________________________________________________

    Workaround 2: Mount your Windows installation media to a folder and manually copy the ATI files to the \Windows\winsxs directories (choosing to overwrite the files if they exist). The file names are:

    (x86 versions)

    x86_atiilhag.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4c2c9aec5f3d44b5

    x86_atiilhag.inf_31bf3856ad364e35_6.1.7600.16385_none_a574bbd4a69c292d

    (I am struggling with this because I’m not sure of the procedure here or the how).

    Thanks Guys for all your assist on this issue!
    Jimsan

    • Hi Jimsan,

      Thank you for contacting HackSys Team – Panthera.

      Thank you for leaving back the comment.

      Jimsan, the best and the effective way to fix this issue is by doing in-place upgrade of Windows 7.

      You won’t lose any data. It’s a kind of repair install of Windows.

      Please let us know if you do not have the download link of the Windows 7.

      Please reply back with the Windows 7 Edition which is installed on the Computer that has this issue.

      Please mention whether it’s 32 bit or 64 bit.

      Regards,
      HackSys Team – Panthera
      http://hacksys.byethost2.com/
      hacksysteam@hotmail.com

  4. Over the past few months have not been able to load Vista sp1 without errors then yesterday I came across your script v1.3 and ran it. Did it’s job without a hitch! Before running Sp1 again I uninstalled the virus software as before and restarted at a clean boot. Ran sp1 and it showed 100% complete for all three stages, but alas still getting the same results as all the other times with the error message “Service Pack did not Install. Reverting changes. Error Code: 0x800f0826”.

  5. Looks like a good script, tried this as a last resort to get SP1 installed on Win7, having tried all suggestions Microsoft had to offer. Sadly though, still no joy – download fails at 19% everytime. Giving error code 0x80073701

    • Hello Rob,

      Thank you for contacting HackSys Team – Panthera.

      Error: 0x80073701 while trying to update via Windows Update

      We are sorry to hear that the issue is still unresolved.

      Please try out these steps and let us know if that works or not.

      Action Plan:

      1. Uninstall the security software and reboot the Computer.
      2. Put the Computer to clean boot.
      Link: http://www.vfreaks.com/vfreakslab/winga/perform-clean-boot-in-windows-vista-or-windows-7.html

      3. Download and install the stand alone installer of the Service Pack or the particular update that is failing.

      If after trying these steps and the issue is not fixed, please reply back with the following details.

      Q1. Is that a 32bit or 64bit OS?
      Q2. Which Update is failing? Please name the KB number.

      Please attach the following log files and send it to us.
      1. C:\Windows\windowsupdate.log
      2. C:\Windows\Logs\CBS\CBS.log
      3. C:\Windows\Logs\CBS\Checksur.log
      4. C:\Windows\inf\setupapi.dev.log

      Please zip the log files and send it to us for further analysis.

      Regards,
      HackSys Team – Panthera
      http://hacksys.vfreaks.com/
      hacksysteam@hotmail.com

      • Hello Rob,

        Thank you for contacting HackSys Team – Panthera.

        Error: 0x80073701 while trying to update via Windows Update

        We are sorry to hear that the steps did not help.

        After reviewing the log files it seems there are many corrupt Windows Component files.

        These are few offending packages I found in CBS.log file.

        Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514

        Microsoft-Windows-Common-Modem-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514

        Microsoft-Windows-Common-Modem-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.INF_mdmjf56e

        Package_for_KB976933~31bf3856ad364e35~amd64~~6.1.7601.17514

        Action Plan:

        1. Unintall the offending packages. Open command promt as Administrator and type these commands and press Enter.

        a) start /w pkgmgr /up:Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514

        b) start /w pkgmgr /up:Microsoft-Windows-Common-Modem-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514

        c) start /w pkgmgr /up:Microsoft-Windows-Common-Modem-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.INF_mdmjf56e

        d) start /w pkgmgr /up:Package_for_KB976933~31bf3856ad364e35~amd64~~6.1.7601.17514

        2. Reboot the Computer in Clean boot and do not enable the security software.

        3. Download and run TDSSKiller Rookit Removal tool. Note: If it find any Rootkit infection, please remove it and reboot the Computer.
        Link: http://support.kaspersky.com/downloads/utils/tdsskiller.exe

        4. Download and do full Virus scan using SuperAntiSpyware Poratble version. Note: If it find any Rootkit infection, please remove it and reboot the Computer.
        Link: http://www.superantispyware.com/sasportable.php

        5. As there are more than 200 errors found in CheckSur.log and CheckSur was not able to repair it. We will have to run Windows Update Troubleshooter script again.

        6. Be sure to download the fixit and CheckSur (System Update Readiness) tool before running the Windows Update Troubleshooter script.
        Link: http://support.microsoft.com/kb/947821

        7. After Checksur and Windows Update Troubleshooter script is done, reboot the Computer.

        Please attach the following log files and send it to us.

        1. C:\Windows\windowsupdate.log
        2. C:\Windows\Logs\CBS\CBS.log
        3. C:\Windows\Logs\CBS\Checksur.persist.log
        4. C:\Windows\inf\setupapi.dev.log

        Please zip the log files and send it to us for further analysis.

        Regards,
        HackSys Team – Panthera
        hacksysteam@hotmail.com
        http://hacksys.vfreaks.com/

        • Hello Rob,

          Thank you for contacting HackSys Team – Panthera.

          Error: 0x80073701 while trying to update via Windows Update

          Unfortunately, the steps did not help to fix the issue.

          We are freelancers who take security projects from clients. We are Technical Consultant of vFreaks Technical Support.

          Rob, after review the CheckSur.persist.log, we found that the level of corruption of the CBS Manifest files are high.

          Snip from Checksur.persist.log

          =================================
          Checking System Update Readiness.
          Binary Version 6.1.7601.21645
          Package Version 13.0
          2012-02-01 13:11

          Checking Windows Servicing Packages

          Checking Package Manifests and Catalogs

          Checking Package Watchlist

          Checking Component Watchlist

          Checking Packages

          Checking Component Store
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft.windows.h…sensor-driverclass_31bf3856ad364e35_6.1.7600.16385_none_e7478ca10d982ee7 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_ehcir-nonmsil_31bf3856ad364e35_6.1.7600.16385_none_3e713c9e54aaa9b2 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-s..-mceauthorscriptreg_31bf3856ad364e35_6.1.7600.16385_none_aff52f6dddc7ed0d identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-ehome-adms_31bf3856ad364e35_6.1.7600.16385_none_29154acae4247c8f identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-e..orkexplorersettings_31bf3856ad364e35_6.1.7600.16385_none_0d29da7ff093e63c identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-tpm-driver_31bf3856ad364e35_6.1.7600.16385_none_556f4e0ad316b10b identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-power-policy-legacy_31bf3856ad364e35_6.1.7600.16385_none_12f7b2ebd324e037 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-s..dsubsystem-policies_31bf3856ad364e35_6.1.7600.16385_none_6c10ceb0d7573236 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-webservices-events_31bf3856ad364e35_6.1.7600.16385_none_f49d1ef8d90c4c73 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-tpm-tbs_31bf3856ad364e35_6.1.7600.16385_none_ee8e2b18d9a7e398 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-branding-shell_31bf3856ad364e35_6.1.7600.16385_none_338190a2db506b03 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-s..ugc-instrumentation_31bf3856ad364e35_6.1.7600.16385_none_ce88703adbb149ce identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-d..eashared-imepadhelp_31bf3856ad364e35_6.1.7600.16385_none_d2009c19dbffe5da identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-wininit-events_31bf3856ad364e35_6.1.7600.16385_none_7d8e4341ddaa9aa7 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity wow64_microsoft-windows-i..guagegroup-japanese_31bf3856ad364e35_6.1.7600.16385_none_36c5f2cddf541aac identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_macrovision-protection_31bf3856ad364e35_6.1.7600.16385_none_bceec1cde0ba81e6 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-imapi_31bf3856ad364e35_6.1.7600.16385_none_547da2bbe0e7763d identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-loadperf-events_31bf3856ad364e35_6.1.7600.16385_none_29942c0ce3a6b0cc identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-installshield-wow64_31bf3856ad364e35_6.1.7600.16385_none_d0bf3aede4fc0ce9 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-nx_31bf3856ad364e35_6.1.7600.16385_none_4ce4a32ee52ccb15 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-t..rk-dummytextservice_31bf3856ad364e35_6.1.7600.16385_none_9a88ad46e6a168a9 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity wow64_microsoft-windows-com-dtc-vistasp1_31bf3856ad364e35_6.1.7600.16385_none_b4279533e72f185d identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-tcpip-nettcpip_31bf3856ad364e35_6.1.7600.16385_none_49d87306e9c0fd77 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-s..onfiguration-client_31bf3856ad364e35_6.1.7600.16385_none_1da87e1aea354aa8 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-fatformat_31bf3856ad364e35_6.1.7600.16385_none_ee881235ea47311d identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-eaime-all_31bf3856ad364e35_6.1.7600.16385_none_eb0fa3e0ed5721cc identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft.windows.h..er.dot4-driverclass_31bf3856ad364e35_6.1.7600.16385_none_6a5a2a4bee13754e identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-i..odepage-core-hebrew_31bf3856ad364e35_6.1.7600.16385_none_639abc6aeec71604 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity wow64_microsoft-windows-shell-registration_31bf3856ad364e35_6.1.7600.16385_none_27f6488deeed2f0a identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-interface_31bf3856ad364e35_6.1.7600.16385_none_d4877e19f0e97e54 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft.windows.h..nfrared-driverclass_31bf3856ad364e35_6.1.7600.16385_none_306f2a98f331175a identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-s..once-registry-entry_31bf3856ad364e35_6.1.7600.16385_none_244a0846f33e1b78 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-pstore-data_31bf3856ad364e35_6.1.7600.16385_none_3d8b904df3443537 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity wow64_microsoft-windows-i..roup-western_europe_31bf3856ad364e35_6.1.7600.16385_none_7d669faef344ab0a identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-m..s-components-jetvba_31bf3856ad364e35_6.1.7600.16385_none_7568a7acf374dfed identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-pnpinstaller_31bf3856ad364e35_6.1.7600.16385_none_eeafc93df5d83e81 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft.windows.h..idclass-driverclass_31bf3856ad364e35_6.1.7600.16385_none_a1a165a8fbb88ee4 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-d..ptechnologies-fonts_31bf3856ad364e35_6.1.7600.16385_none_59f2e781fd9c0ba8 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7600.16385_none_a627b893fdbe3637 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity msil_microsoft.web.manag..nt.aspnet.resources_31bf3856ad364e35_6.1.7600.16385_en-us_325e5be4faca0c8e identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-ie-extensionmanager_31bf3856ad364e35_8.0.7600.16385_none_c4d4cc64081a0e15 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-ie-administrationkit_31bf3856ad364e35_8.0.7600.16385_none_13cad71d877cded5 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-w..vironment.resources_31bf3856ad364e35_6.1.7600.16385_en-us_7730bb201e69122a identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity wow64_microsoft-windows-w..vironment.resources_31bf3856ad364e35_6.1.7600.16385_en-us_8185657252c9d425 identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-i..gbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_1eab13b65d3f791e identity and keyform do not match; keyform is wrong.
          (f) CSI Corrupt Component Keyform 0x00000000 identity wow64_microsoft-windows-i..gbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_28ffbe0891a03b19 identity and keyform do not match; keyform is wrong.

          Summary:
          Seconds executed: 1548
          Found 252 errors
          CSI Corrupt Component Keyform Total count: 252

          As you see that there are 252 corrupted manifest files, it’s very difficult to fix all of them manually. The best next step suggested by us are as follows.

          1. Uninstall all the Security Software installed on the Computer including SpyBot.

          2. Do a repair install of Windows 7.

          Please let us know if you need in doing the repair install of Windows. We will be happy to help you.

          Regards,
          HackSys Team – Panthera
          hacksysteam@hotmail.com
          http://hacksys.vfreaks.com/

  6. Worked like a charm. Thanks so much.

  7. BigGtheDood says:

    Your WindowsUpdate.ver1.3 did not work for us, we still cannot update Windows 7 Service Pack 1 for x64-based Systems (KB976932).

    • Hi,

      Thank you for contacting HackSys Team.

      We are sorry to hear that the issue is not fixed after running the Windows Update Troubleshooter v1.3 script.

      To help you better, please reply to this email with the details.

      Q1. What is the error code that you are getting while installing Service Pack 1?
      Q2. What is the security software installed on the issue Computer?

      Regards,
      HackSys Team – Pantherahacksysteam@hotmail.com

      http://hacksys.vfreaks.com/

  8. Thanks for the script, although it didn’t fix my problem. It seems that Windows Update has an issue with Intel Matrix Storage Manager 8.9.0.1023. After updating/upgrading the program with Intel Rapid Storage Technology 10.8.0.1003 everything works fine.

  9. Very good information. I had an update that was trying unsuccessfully to install when shutting down computer. It just kept trying until I forced a shutdown. Didn’t need to run script at least for now. I was able to install the latest “update agent” and that appears to have resolved issues for now.

    Thanks for posting. I almost always find help anywhere other than Microsoft website.

  10. My most sincere thanks for your v1.3 windows update fix. I have spent weeks on and off trying every fix on the microsoft site multiple times for w7 sp1 and nothing worked. Once I used your fix it loaded first time. Again, thank you very, very much.
    Matt

  11. Daniel Hrvatin says:

    Hi guys

    I have been having some MAJOR issues with my windows on a number of my machines. Im running windows 7 64 and 32bit on a couple machines and lately im always getting validation errors on a number of programs as well as certificate issues. One major one is with iTunes saying it does not have a valid certificate as well as the program attempting to load with the status bar showing for 1second and then vanishing leaving the program not to install at all!

    • Hello Daniel,

      Thank you for contacting HackSys Team.

      We are sorry to hear that you are facing such issues with your Windows.

      Do not worry, we will try our best to fix this.

      May we know the operating system installed on the issue Computers?

      Try to check the CMOS battery. Try to check if the System Date and time is set correctly.

      Please give more detail about your issue. If you are getting any error message, please let us know the exact error message. Screenshots are more preferred.

      Regards,
      HackSys Team – Panthera
      hacksysteam@hotmail.com
      http://hacksys.vfreaks.com/

  12. Ninfa Boldosser says:

    That was a great line. I enjoyed it very much. Ninfa Boldosser

  13. Thanks! Finally I was able to install SP1 on a Win 7 Home Edition. Tried a lot of steps seperately, but always failing at 99% with 0x80041002. With your script it ran in one go!

    BTW, do I need to reset any of the settings afterwards? Like the UAC (which I checked and it was set ok actually)…

    Cheers!

    • Hello,

      Thank you for trying Windows Update Troubleshooter v1.3 script.

      We are glad to hear that your issue has been resolved and you are happy.

      We are glad to announce that vFreaks Technical Support is done a fund raise of 50000$.

      HackSys Team is the core Technical Consultant of vFreks Technical Support.

      Please be connected for more updates from HackSys Team.

      Regards,
      HackSys Team – Panthera
      http://hacksys.vfreaks.com
      hacksysteam@hotmail.com

  14. Hi,

    I still can’t belive my eyes… After all the things I did – Windows Update works again and thanks to your Windows Update Toubleshooter.

    Huge thanks! You are great!

  15. Got as far as restarting the update service, but then responded with “Windows Resource Protection could not start the repair service” when trying to run the System File Checker.

  16. Hello Friends,

    We have updated Windows Update Troubleshooter v1.3 & v1.2 Scripts. As suggested by Microsoft Answers Forum, we have removed the Disable UAC function from the Scripts.

    Here are the updated links:

    Windows Update Troubleshooter v1.3 : http://hacksys.vfreaks.com/winupdate/windows-update-troubleshooter-v1-3.html

    Windows Update Troubleshooter v1.2 : http://hacksys.vfreaks.com/winupdate/windows-update-troubleshooter-v1-2.html

    Please feel free to comment on these scripts and give feedback. We look forward for any kind of suggestions.

    Regards,

    HackSys Team – Panthera

    http://hacksys.vfreaks.com/

    hacksysteam@hotmail.com

  17. Jennifer Roth says:

    I don’t have a “clean boot” option. All I have is safe boot. Your fix stopped working after the log.

    • Hello Jennifer,

      Thank you for contacting HackSys Team.

      We are sorry for the delayed response. We are always there to help you with any issues related to Windows.

      To help you better, we want to ask few basic question so that we can analyze the cause of the issue. Please reply to this email with the answers of this following questions.

      Q1. Which Operating System you are using like Windows XP/Vista/7.
      Q2. Is that a 32bit or 64bit Operating System?
      Q3. From how long you are facing this issue?
      Q4. Which Security Software is installed on the Computer like Norton, Mc.Afee, AVG, etc?
      Q5. What is that exact error message or the error code you are getting while installing Windows Update?

      If you want live help from Certified Expert Technicians, you may connect to our Official Technical Support Partner.
      Company: vFreaks Support (Support for Windows XP/Vista/7/Server at affordable price).
      Website: http://www.vfreaks.com/

      Get Live Help from Certified Expert Technicians instantly.

      Regards,
      HackSys Team – Panthera
      hacksysteam@hotmail.com
      http://hacksys.vfreaks.com

  18. Hello All,

    We are glad to announce that we are now the official technical consultant for vFreaks Technical Support.

    Thank you all for your support and co-operation and making us better in this field.

    We are always there for you all. If you have any suggestions and want to contact us for any project, you are always welcome.

    Regards,

    HackSys Team – Panthera

    http://hacksys.vfreaks.com/

    hacksysteam@hotmail.com

  19. Well I can’t say enough about this. I had so many problems with Win Update it was untrue but now no longer. I am a happy little bunny. Thankyou Hacksys.

  20. Why is Clean Boot needed? Will updates have to be performed in a clean boot or will this script fix all issues?

    • Hello Chris,

      Thank you for contacting HackSys Team.

      Clean Boot is an important steps. Please take a note.

      Q: What is Clean Boot in Windows?
      Ans: Clean Boot is a system state where all Non-Microsoft services and Startup items are disabled.

      Q: How will it help?
      Ans: It is found that 40-45 % of the issues on Windows are fixed by doing Clean Boot. Windows Update failure happens due to many factors like:
      1. Issues Caused by Security Software.
      2. System File Corruption
      3. Servicing Components missing from winsxs folder.
      4. Interruption by any Non-Microsoft software that are installed on the Computer.
      5. Hardware issues.

      This script does most of the Windows Update Troubleshooting steps by its own. We cannot guarantee that this will fix the issue every time.

      Hope this helps.

      Regards,
      HackSys Team – Panthera
      http://hacksys.vfreaks.com

  21. Sorry microsoft but you failed, you are the winner. You have an excellent script.

    • Hello Cred,

      Thank you for trying Windows Update Troubleshooter Script.

      We are glad to hear that you found it useful. We are trying to pass this script to most of the people that are having issues with Windows Update.

      But do not know why Microsoft is removing our posts from MS Answers Forum. I think they do not want the people to get helped by others.

      They are marking our Posts as Spam and they are removing it from the forum. If this continues, then I do not think that most of the people out there with Windows Update issues will be able to get helped from us.

      If you do find this Script useful, we will appreciate if you can spread this Windows Update Troubleshooter Script on the net so that friends and people out there can use it to the best.

      You can post about this script to many forums like (Ms Answers, SevenForums, Vistax64 Forum, etc)

      Post Link: http://hacksys.vfreaks.com/winupdate/windows-update-troubleshooter-v1-3.html

      Website Address: http://hacksys.vfreaks.com/

      If you need any further information, please reply to this email.

      Regards,
      HackSys Team – Panthera
      http://hacksys.vfreaks.com/
      hacksysteam@hotmail.com

  22. Wonderful script 1.3.

    Thanx for sharing.

    and Thanx from Paris France

  23. my apologies for a double post but now my restore point i made before this reboot is gone and my laptop is now running slower… any reason why this may be happening??

  24. I tried this and let it go all the way to the last step and rebooted my laptop. then i tried to install the Win 7 SP1 and still failed, any way you can help?

  25. Microsoft fails. You win!

    Thanks so much for this.

    I’d been unable to install Win 7 SP1. did everything MS said to, nothing worked. Only wish I’d found this script sooner.

    Thought of selling it to MS 🙂 You’ve managed what they can’t.

    Thanks again.

    • Hello Mike,

      Thank you for trying Windows Update Troubleshooter.

      We are glad that your issue has been resolved. Please be connected to HackSys Team for more updates coming soon.

      If you have any suggestions, please feel free to leave back a comment. We will try to accomplish the desired request as soon as possible.

      Regards,
      HackSys Team – Panthera
      http://hacksys.vfreaks.com

  26. Many thanks!!!

  27. Hello HackSys Users,

    13th May 2011- Feature add: Added auto download feature. More user friendly. Request by Tim.

    Thank you,

    HackSys Team – Panthera

  28. worked like a charm. great directions and smooth format…thank you

  29. I gave it a go but no luck. Still a very nice tool. One feature I would like is the ability to copy and paste the urls for the downloads or have them be a link.

  30. Went through all the steps but still cant update. The last step with msconfig didn’t seem to work out for me it opened it up but it didn’t look like it made any changes.

    • Hello Tim,

      Msconfig is pulled out at the end so that you can put the Computer to clean boot.
      In clean mode, all the non-microsoft services will be disabled for the later restarts.

      To keep the Computer in clean boot, please follow these steps:
      1. Disable all non-microsoft services
      2. Disable al startup items.

      Regards,
      HackSys Team – Panthera

  31. downloaded the Troubleshooter, clicked to open and all I get is another box titled Windows 20%Update20% v1.2[1].zip when I double click the vbs file nothing seems to happen. Am I missing something or is it not working for some reason?

    • Hi Paul,

      Thank you for trying this script. From the issue it seems that there is some issue with your .VBS file associations.

      Please try to download this VBs fix and check if the issue is resolved. Please leave back comments.

      http://www.winhelponline.com/fileasso/vbsfix_vista.zip

      You may try this command too.

      Open Command Prompt as Administrator.

      Type this command

      cscript.exe %userprofile%\Desktop\Windows Update Troubleshooter.vbs

      Note:

      cscript.exe (path of the vbs file)

      Regards,

      HackSys Team – Panthera

  32. chief wei says:

    2011-04-13 13:56:58:881 1000 108c DnldMgr FATAL: DM:CAgentDownloadManager::LoadUpdateMetadataFromDatastore: GetUpdates failed with 0x80248007.

    2011-04-13 13:56:58:881 1000 108c DnldMgr FATAL: DM:CAgentDownloadManager::LoadUpdateMetadataFromDatastore: GetUpdates failed with 0x80248007.

    2011-04-13 13:56:58:881 1000 108c DnldMgr FATAL: DM:CAgentDownloadManager::LoadUpdateMetadataFromDatastore: GetUpdates failed with 0x80248007.

    2011-04-13 13:56:58:881 1000 108c DnldMgr FATAL: DM:CAgentDownloadManager::LoadUpdateMetadataFromDatastore: GetUpdates failed with 0x80248007.

    • Hello Wesley,

      May I know when you are getting this error? From the error it seems that this is an issue with CheckSur (System Update Readiness Tool).

      Regards,
      HackSys Team – Panthera

  33. Worked like a charm….

    Thank you..:-)

  34. chief wei says:

    Still the problem.

  35. Tried you script but it ran as far as Launching System File Checker Scan. Still reporting 0x80070005 errors as per below

    2011-04-23 07:30:41:612 708 d1c Setup WARNING: CBS EvaluateApplicability returned error, error = 0x80070005

    2011-04-23 07:30:41:612 708 d1c Setup FATAL: Applicability evaluation for setup package “WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226” failed, error = 0x80070005

    2011-04-23 07:30:41:612 708 d1c Setup FATAL: SelfUpdate check failed, err = 0x80070005

    2011-04-23 07:30:41:613 708 d1c Agent * WARNING: Skipping scan, self-update check returned 0x80070005

    2011-04-23 07:30:41:671 708 d1c Agent * WARNING: Exit code = 0x80070005

    2011-04-23 07:30:41:672 708 d1c Agent *********

    2011-04-23 07:30:41:672 708 d1c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]

    2011-04-23 07:30:41:672 708 d1c Agent *************

    2011-04-23 07:30:41:672 708 d1c Agent WARNING: WU client failed Searching for update with error 0x80070005

    • Tj,
      From the above listed error it seems that there is some issue with Windows Update Agent. So, try to download and install the latest Windows Update Agent. If you have issues with the script, please reply back the Error Message.

      Regards,
      HackSys Team – Panthera

  36. Brilliant stuff … worked when multiple attempts at convoluted other solutions would not.

    Many thanks.

    • You are most welcome. We at HackSys Team value your valuable input and feedback.

      If you have any suggestions, you are welcome.

      Thanks,
      HackSys Team – Panthera

  37. Hello HackSys Users,

    17th March 2011- Bug Fixed : Unable to launch Microsoft Fixit and System Update Readiness Tool (CheckSur).

    Thank you,

    HackSys Team – Panthera

  38. Brilliant script.

    Loved it…

    Thank you

  39. Thanx solved my big problem.

    Thankkkk yoooouuuuu sooo muuucchhh….

  40. invisible_underground says:

    Thank you for the wonderful script.

    Can you explain what to do do when it prompts to download the files?

    I’m a bit confused.

    Help!

    Thanx in advance.

    • There is not much that can be explained here.

      When it gives you the option to download the Microsoft Update Reset Fixit, I guess there it shows the download link.

      Download the file from the link and place it exactly in the location mentioned in the message box.

      Thank you

  41. Thank you HackSys Team,

    Saved me from re-formatting my hard drive due to buggy Windows Update.

    HackSys Team rocks….

  42. Wonderful script.

    Thanx for sharing.

Leave a Reply

Your email address will not be published. Required fields are marked *