Hello, well, this is not a VISTA update error, and the Vista solutions do not seem applicable.Error 8000FFF unspecific error started a few weeks ago and Windows "7" Beta will not update, of course if you try to update manually it will simply redirect back to the windows update site and open the windows update on the local system.I find it hard to believe that I am the only one with this error?I have changed permissions, lowered security shut off anti-virus (removed it actually) shut off Defender and still all updates result in the same error.I have also run several anti malware and virus scan and the system comes up clean everytime.it is a :older Sony VAIO with a 1.73 Ghz , 786 RAM, with 1.7GB Readyboost thumb drive, an 80 gig primary drive with a 232 Gb secondary drive. A GE Force 6200 with 512 Mb Video cardso if meets therequirements for the unit to run.any suggestions of places I have not gone,I have checked the registery for the Vista fixes and they are not in WIN7.OKany advise would be helpfullJones

I also have this problem. Last successful update was on the 23rd of Febuary. I'm not sure what I did wrong. I cannot recall having done anything major changes to the system.

try this fix:http://support.microsoft.com/kb/946414/en-us

I, too, have this issue. I looked at KB946414 and I have no reg keys like this. I followed the steps outlined for Vista OS in general (stop update service, delete SoftwareDistribution folder) and still no go. Even added the various websites just to play it safe!

Have you tried running the Windows Update troubleshooter?

Hello again, no the fix outlined above does not work as that is a VISTA fix, Win 7 Beta does not have those componets.as for the Troubleshooter, (as much as I really like the concept) it also does not work.still looking all over the place for a fix,as for MS they will not help on the Win 7 Beta (so far) however I am trying to be persuasive.Jones

Try these commands:Wevtutil sl Microsoft-Windows-Bits-Client/Analytic /e:true sc qc bits net start bits sc queryex bitsThen post these files online somewhere:%SystemRoot%\System32\Winevt\Logs\Microsoft-Windows-Bits-Client%4Analytic.evtx%SystemRoot%\System32\Winevt\Logs\Microsoft-Windows-Bits-Client%4Operational.evtx

From the KB article for Vista, this appears to be a corruption in the stuff that Windows Update is expecting to find when it checks for stuff that still needs doing.So, locating and deleting those entries in their Windows 7 locations is the most likely fix. Beyond that, you'll have to locate the Windows Update log files to get more information on the errors. How to read the Windowsupdate.log file- John

I guarantee you are not the only one with this error. I have tried everything that has been posted, including uninstalling all updates one at a time. Seems everyone can read the error code, but does not understand that this is Windows 7 Beta. I know there has to be a fix some where other than reloading Windows 7. I have searched and all direct you to the Vista Fix. There is nothing in the registry that even resembles the entries that the fix states, plus I seached the Reg to is if it might be found elsewhere. The update that was stated to remove is not an update that I installed. I have two vista machines that are running with out update errors. Someone on this forum has the answer, I just hope that it is not what I first suspected. Did Microsoft turn off updates for this beta? I usually can fix most issues, but update errors have always been a hit or miss repair. Other than this Windows 7 has run flawlessly.Thanks for any help.John

There's another thread with a similar issue found herethat might have information that could be helpful.

As Wolfie2k6 suggests there is another post open that deals with the same issue. I had the same problem and just done a clean install and problem solved.

Just toupdate everyone who hasn't seen the other thread, it would seem an "In Place Upgrade" tends to cure this problem. We're not entirely 100% sure why this happened, or what, but a reset ofthe OS followed by a Windows Update appears to fix whatever went wrong. An In Place Upgrade involves taking your Windows 7 beta DVD and booting from it, and installing the OS on top of whatever you've got installed. It will NOT wipe out your data files, nor will it uninstall your apps. It just refreshes the OS to it's default state. You will need to download your updates again though.

I also have this issue on my Lenovo X60T.All tips do not work. I have not tried the "In Place Upgrade" yet, but it does make me think about the bugs in windows 7. After all for an average user the tips provided were challenging enough, going through frontiers not many dare. To lastly hear that one has to boot from the the Windows 7 boot DVD for such a small issue, is something dramatic! This will probably be kind of a reinstallment of windows. Since I am running version 7000 I have doubts if this will go right. After microsoft did warn that installments after february would not be possible. So in esscence everyone with this problem running version 7000 is stuck. I hope this will not be the case in the final marketed licence that windows will provide. In that case: Shame on Microsoft! They have had more than enough experience to get rid of these issues!

After working on this issue for almost a month, I took the plunge and ran the disc from inside windows 7. Boot from with in windows and tell it to do an update. It will load all the files and do a reboot. If you are running a duel boot system, like I am it will pause for you to choose the correct OS. Be sure to remove the windows 7 boot disk prior to the reboot. If not it will try to load from disk and if you pick update, at that time, it will tell you that you must do this from within windows. Just remove disk and reboot and it will take over from there. I did not loose any files or programs that I had previously loaded. It was a rather simple upgrade. I agree you should not have to do this, for this kind of error, but several of us spent many hours trying to prevent from a reinstall. This was probably the first time that I did not have any issues with an upgrade from Microsoft. It did fix the issue. Good luck!!

wevenhuis - First of all, this software is BETA. That means it has bugs, it isn't perfected yet and there WILL be problems. Beta testing software isn't meant for the feint of heart. Everyone WAS warned that bad things could happen before they downloaded the ISO. Microsoft did NOT say you can't install after February. They DID say you can't download the ISO after February. If you were smart, you burned the ISO to a DVD and put it in a safe place. You can install it as many times as you please - at least, until July 31st. After that, it'll be a moot point given the BETA will have expired. If you bothered reading what everyone who's done the procedure has written, the In Place Upgrade:a.) Did NOT damage or remove their existing data b.) Did NOT remove their programs and most importantly,c.) FIXED THE PROBLEM!All the "In Place Upgrade" does refresh the OS. It straightens everything out and makes it so you can get on with your life.Also, had you botheredreading the linked threads posted early on in the various threads, Microsoft HAS a fix for the issue - under Vista. You download the updated Windows Update engine and install it manually. Unfortunately, that fix only applies - thus far - to Vista. No doubt, once Windows 7 is released to the general public, they will update that which needs to be updated and will make the fix available to Windows 7 as well.

Also, had you botheredreading the linked threads posted early on in the various threads, Microsoft HAS a fix for the issue - under Vista. You download the updated Windows Update engine and install it manually. Unfortunately, that fix only applies - thus far - to Vista. No doubt, once Windows 7 is released to the general public, they will update that which needs to be updated and will make the fix available to Windows 7 as well. FYI since you are very keen on sharing accurate information: the update is not a universal "fix" though it have worked for some.I too have spent countless hours searching for a solution and reinstalling updates and applications. Today's lesson is if the issue exist also in Windows 7, there's no reason for me to consider an upgrade.