Windows Modules Installer Error:126

HiTommyPaul,

Thank you for visiting Microsoft Answers.

I have few steps which might help you.

Method 1

Check if Windows Update Service is selected as start.

To do this, follow these steps:

    1.Click on Start, Run and type the following command in the open box and click OK.

      In services.msc find the Automatic Updates service and double-click on it.

1. Click on the Log On Tab and make sure the "Local System Account" is selected as the logon account    and the box for "allow service to interact with desktop" is UNCHECKED.
2. Under the Hardware Profile section in the Log On Tab, make sure the service is enabled.

  3. On the General Tab, the Startup Type should be Automatic, if not, drop the box down and select   Automatic.

 4. Under "Service Status" on the General tab, the service should be Started, click the Start button enable it.

 Repeat the steps above for the service "Background Intelligent Transfer Service (BITS)".

 

Method 2

You may also re-register Windows Update DLLs.

To do this, follow these steps:

    1.Click on Start, Run, and type CMD and click ok

    2.In the black command window type the following command and press Enter

      REGSVR32 WUAPI.DLL

      Wait until you receive the "DllRegisterServer in WUAPI.DLL succeeded" message and click OK.

    * Repeat the same step for each of the following commands:

      REGSVR32 WUAUENG.DLL

      REGSVR32 WUAUENG1.DLL

      REGSVR32 ATL.DLL

      REGSVR32 WUCLTUI.DLL

      REGSVR32 WUPS.DLL

      REGSVR32 WUPS2.DLL

      REGSVR32 WUWEB.DLL

 

Method 3

Remove the corrupted Windows Update Files. To do this, follow these steps:

    1. At the command prompt, type the following command and press Enter

      net stop WuAuServ

    2.  At the command prompt,

      type cd %windir% and press Enter

    3. In the opened folder, type the following command and press Enter to rename the  Software Distribution Folder

      ren SoftwareDistribution SD_OLD

     4.Restart the Windows Update Service by typing the following at the command prompt

      net start WuAuServ

 Type Exit and Press Enter to close the command prompt.

1.       Reboot the computer and check if you have similar issue.

2.       Hope the information helps. Please post back and let us know.

3.       Regards,

  Debleena S

Microsoft Answers Support Engineer

Visit our Microsoft Answers Feedback Forumand let us know what you think.

 

Whoever Mike from Microsoft Support Engineers is, you should know that this is not the answer.  To my knowledge, the only answer is to restore the computer to factory default and start over.  I have tried every fix you put up and then some.  I have searched every where on the web to find an answer and can't.  Unfortunately, I can't restore my laptop to factory defaults.  My screen is broken and the laptop has been discontinued.  I run it through my TV and can't afford to get a new one because of this poor economy.  So I, like many people out there have to make due with what I have.  We all need a good true answer to this problem.  There has to be a way for somebody to come up with a valled work-around for this issue, or to give us a way to manualy download the updates wee need.  BUT THE WORST THING YOU CAN DO IS SAY THAT THE ABOVE IS THE ANSWER, WHEN AS YOU CAN SEE, IT HASN'T HELPED ANYONE.  BUT THEN AGAIN, I'M SURE NOBODY AT MICROSOFT EVEN PAYS ATTENTION TO THESE THREADS AFTER IT HAS BEEN MARKED AS SOLVED.  SO I'M SURE I JUST WASTED ANOTHER 5 MINUTE OF MY LIFE TYPING THIS OUT FOR NOBODY TO READ.

The problem is, that Microsoft Support seems to have been sold out to overseas support and they only know how to search the web and answer questions that already have solutions on the web.  I have an existing case no (1146319490) open on this same issue on my computer, and they have not even found this answer yet to have me try.  Instead, I've got passed around between internet explorer (which won't open and thus services.msc fails to use IE components too).  All they know how to do is an "upgrade install" or "install repair" or some other nonsense.  No one who really understands how the OS works is reachable or responsible for figuring out a repair procedure for these kinds of problems.  There are no "audits" built in or available which can "validate" each services needed configuration/dll set etc.

Microsoft wonders why the number of people in the Apple stores has grown so large?  I'd guess it is because people are tired of losing their data/lives to this nightmarish problem of "there is no such thing as windows support".

In the end, my support ticket is still open because I need to find my installation disk so that we can do an "install repair" to fix the missing/corrupted files.  It seems just strange...

This nonsense has persisted so long in the world of Windows that people just think it is the thing to do...

Sad state of affairs we have here.

Wubs

The problem is, that Microsoft Support seems to have been sold out to overseas support and they only know how to search the web and answer questions that already have solutions on the web.  I have an existing case no (1146319490) open on this same issue on my computer, and they have not even found this answer yet to have me try.  Instead, I've got passed around between internet explorer (which won't open and thus services.msc fails to use IE components too).  All they know how to do is an "upgrade install" or "install repair" or some other nonsense.  No one who really understands how the OS works is reachable or responsible for figuring out a repair procedure for these kinds of problems.  There are no "audits" built in or available which can "validate" each services needed configuration/dll set etc.

Microsoft wonders why the number of people in the Apple stores has grown so large?  I'd guess it is because people are tired of losing their data/lives to this nightmarish problem of "there is no such thing as windows support".

In the end, my support ticket is still open because I need to find my installation disk so that we can do an "install repair" to fix the missing/corrupted files.  It seems just strange...

This nonsense has persisted so long in the world of Windows that people just think it is the thing to do...

Sad state of affairs we have here.

---

Wubs

I guess that means it's time for all of us to boycot windows and start buying Apple products.  And the funny thing it,  I search apple .dll's on the web, or go to apple support, I get everything I could ever want and mere.  You can copy these files from your friends who have the same opperating system, and install them with no problem.  I have given up on fixing the problem with the laptop that I have this problem on.  I have a toshiba with windows 7 on it that works fine.  I have the recovery disks and I made the repair disks and a system immage and backup on it.  In about 2 or 3 years when the processor finnaly fails on it, I will buy an Apple and will be done with Windows forever.

IF MICROSOFT WANTS TO KEEP THEIR LOYAL CUSTOMERS LIKE ME, THEN THEY NEED TO GET REAL TECHNICIANS HERE IN THE UNITED STATES WHO KNOW THE SYSTEM INSIDE AND OUT TO ASSIST US IN FIXING THESE PROBLEMS.  WE ARE ALL TIRED OF THIS AND WE'RE NOT GOING TO KEEP WASTING OUR MONEY ON THIS NOW INFERIOR PRODUCT JUST BECAUSE IT IS A LITTLE MORE COMPATABLE WITH THE WORLD THE APPLE IS.  AT THIS POINT, APPLE IS 98% COMPATABLE WITH EVERYTHING OUT THERE AND 98% IS GOOD ENOUGH FOR ME.

I was missing the following registry key: 

HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version.

To fix it:

1. Navigate to C:\Windows\Servicing\Version and read the name of a subfolder. It will be named something like 6.1.7600.16385. That is your {TrustedInstaller ID}. Copy the name of that folder to the clipboard (and paste it in Notepad for safe keeping). 
2. Find a subfolder in C:\Windows\WinSxS whose name starts with:

x86_microsoft-windows-servicingstack_31bf3856ad364e35_{TrustedInstaller ID} (32bit Windows)

amd64_microsoft-windows-servicingstack_31bf3856ad364e35_{TrustedInstaller ID} (64bit Windows)

Copy the name of that folder to the clipboard (and paste it in Notepad for safe keeping).

3. Create subkey "HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version". You will need to take ownership of "Component Based Servicing" then give yourself full access permissions before you can create the key.
4. In the new Version key, create an "expandable value" using the TrustedInstaller ID as its name and the complete path of the folder you identified in WinSxS as its value. Properly you should use %SystemRoot%\WinSxS\whatever instead of C:\Windows\WinSxS\whatever.

This absolutely fixed my problem with sfc /scannow

Thank you.