We just released another Fix it Knowledge Base (KB) article. This Fix it resolves error code 0x8000FFFF when you click check for updates using Windows Update as described in KB 946414.
This didn't work for me. I still get an error message that Windows can't check for updates.
Thank you for taking the time to provide feedback. Would it be possible to e-mail us the WindowsUpdate.log file located in c:\windows? The WindowsUpdate file will provide information that should allow me to narrow down why Windows Update is failing for you. If we can determine why it is failing we can then update the Fix it solution so that it helps others that run into the same issue you did.
If you need immediate assistance, please use "Get Help Now" link at the top right of the Knowledge Base article.
Thanks for the fix. It worked great. I appreciate the help.
Thank you Gary! There are a large group of people working to make sure we can deliver automated solutions to you.
Please feel free to check our Facebook group called Microsoft Product Quality Online.
get message backup failed error 8x000ffff. any idea's. thanks
I still receive the error of 0x8000FFFF even after trying to fix. The fix constantly fails. Is this a Vista/Windows update issue? I reverted back to 12/5, when all of my updates went fine, and I am still having the same problem.
What is error code 2738 that occurs once the "fix it" fails?
Thank you for taking the time to send us feedback. 0x8000FFFF usually represents “generic” failures for which the program is not able to identify the exact cause at the time the failure occurs.
You can check to see if the Volume Shadow Copy service is set to Manual and is not disabled.
In the Start Search field type services.msc and press the enter key
In the Services console scroll down the list until you get to Volume Shadow Copy
If the service states it is Disabled in Startup Type column the double click to open the properties
Select the Startup type drop down list and select Manual
Close the services console
Attempt to run the backup again
This issue is a bit outside of the Windows Update Fix it that we released for the 0x8000FFFF error. If the above steps do not resolve your issue you can open a support incident by using the “Get Help Now” link at the top right of any of our Knowledge Base articles.
Hello Kayak Gal,
Thank you for taking the time to post a comment. The MSI is failing to run due to not being able to call VBScript.
Can you go through the following steps to see if this resolves the 2738 error?
1. Run Command Prompt as administrator
a) Start Menu -> All Programs -> Accessories
b) Right click on Command Prompt and select Run as administrator
2. If you are using 32-bit version of Windows:
Type cd %windir%\system32 into the Command Prompt and hit Enter
If you are using 64-bit version of Windows:
Type cd %windir%\syswow64 into the Command Prompt and hit Enter
3. Type regsvr32 vbscript.dll into the Command Prompt and hit Enter
Worked like a charm. Thank you so much!
Thanks for the help. I finanlly found the right website for help. I've been dealing with the problem for 2 months now.
Christine Smith and mikerue,
Thank you so much for your feedback. There are a lot of folks working to provide these solutions. All the responses let us know how we are doing.
If you are interested in seeing more information about these activities, please feel free to visit/join our Facebook group called 'Microsoft Product Quality Online'.
I have followed this procedure and I still am not able to find Windows updates. Any other solutions?
I have an ACER 5310 Laptop running Vista Home Basic (32 bit), which has refused to update for over a year.
I ran the "Fix Windows Update error 0x8000FFF" tool as suggested, but upon invocation the tool helpfully reports:
> This "Fix It" does not apply to your system.
I therefore attempted to edit the registry manually, as per the instructions on
Your instructions say to remove the following key:
I have located in the registry the following key:
which is very similar but note the subtle difference in the spelling of "PendingXmlldentifier".
Is this simply a misprint in the instructions (in which case Microsoft really ought to take more care when providing instructions for something as crucial as the editing of registry keys), or are they indeed different keys?
Thank you for taking the time to post a comment. After doing some digging around there is a good chance that the article is in fact incorrect.
The reason you got the message "This "Fix it" does not apply to your system" is because we check for the existance of the three values called out in the Knowledge Base (KB) article. If one exists then the Fix it runs. If none exist then the message you encountered is displayed.
The main reason we opened up feedback through our blog and e-mail is for this exact reason. If the article is incorrect then our Fix it is as well and we would like to make it so both are correct.
Can you export your components registry key using the following command so we have a backup?
* Select Start > All Programs > Accessories
* Right mouse click on "Command Prompt" and select "Run as administrator"
* In the command prompt type the following without the quotes and hit enter
"reg export hklm\components %userprofile%\desktop\components.reg"
* Next type the following without the quotes and hit enter
"reg delete HKLM\Components /v PendingXmlIdentifier"
* Reboot your machine and attempt Windows Update againt to see if this resolves your 0x8000FFFF error.
Please let us know if this resolved your issue. If it did I will have the Fix it and KB updated with the correct information.
I want to thank you again for taking the time to provide this information. If it works making these changes will also help countless other users.