Checksur.log Cbs Registry Error
Contents |
joscon [Microsoft]May 26, 201043 0 0 0 My last post was on CheckSUR and I wanted to follow it up with how you can use the CheckSUR utility to fix corruption errors that CheckSUR might detect,
Checksur Windows 7
but that cant be fixed with the utility. Typically, the way that CheckSUR works is how to run checksur that it takes the information included with its payload, loads it locally to your machine into the \Windows\CheckSUR directory and then runs checksur.log location the actual executable on the system. As this executable runs, it detects discrepencies in the package store and corrects the errors that it carries a payload for. But, what do you do when you have a package manifest
C Windows Servicing Packages
that shows up in the CheckSUR log but doesnt have the payload with it? If you were to call my team we'll typically try to walk you through getting the files from another server, taking ownership of the servicing directories and moving the files. But what if this is an isolated server? Worse, what if you only have one PC at home and you're having issues? Well, there is an easier way. What you should do
Checksur.exe Location
is identify the package(s) that CheckSUR was not able to fix, they're usually listed at the end of the log. From there, you can take that information and go the Microsoft Download site and pull down the KBXXXXXX.MSU that corresponds to the package that you're seeing failures on. Since you've already run CheckSUR to get to this point, you can copy that .MSU to the \Windows\CheckSUR\packagesdirectory (NOTE: Thisdirectorydoes not exist by default and must be created)and then re-run CheckSUR which will take care of the rest. If you're still having issues afterwards, that just means that something else is going on with the system that is going to require more than CheckSUR can accomplish. Typically, this is true corruption and it may be unrecoverable. As a side note, CheckSUR doesnt have a command line interface component, so you cant rerun it once its been downloaded and installed, you just need to re-run the downloaded MSU package. Hope that helps. -Joseph Tags checksur Comments (43) Cancel reply Name * Email * Website joscon [Microsoft] says: October 6, 2016 at 6:13 am Payload refers to the manifests (package or component), individual component binaries and any additional files required to install an update. These will vary from update to update. Reply joscon [Microsoft] says: October 6, 2016 at 6:13 am Look for those keys in HKLMComponents branch, exp
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums csi payload file missing users FAQ Search related threads Remove From My
System Update Readiness Tool Windows 7
Forums Answered by: SBS 2008 CheckSUR.log Windows Small Business Server > Small kb947821 Business Server Question 0 Sign in to vote Can You Help me? ---cut-here--- ================================= Checking System Update Readiness. Binary https://blogs.technet.microsoft.com/joscon/2010/05/26/using-checksur-and-update-packages-to-fix-corruption/ Version 6.0.6002.22574 Package Version 14.0 2012-05-06 19:07 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_for_KB980195_server_0~31bf3856ad364e35~amd64~~6.0.1.3 Package registry presence failed, possibly an orphaned package on package watchlist (f) CBS https://social.technet.microsoft.com/Forums/en-US/09cebf93-8431-4dfb-aae1-620403fbd070/sbs-2008-checksurlog?forum=smallbusinessserver Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_for_KB2286198_server_0~31bf3856ad364e35~amd64~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_3_for_KB2286198~31bf3856ad364e35~amd64~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_6_for_KB980436~31bf3856ad364e35~amd64~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_for_KB2079403_server~31bf3856ad364e35~amd64~~6.0.1.0 Package registry presence failed, possibly an orphaned package on package watchlist (f) CBS Watchlist Package Missing 0x80070002 Package_137_for_KB948465~31bf3856ad364e35~amd64~~0.0.0.0 Package_6_for_KB980436~31bf3856ad364e35~amd64~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist (f) CBS Watchlist Package Missing 0x80070002 Package_252_for_KB948465~31bf3856ad364e35~amd64~~0.0.0.0 Package_6_for_KB980436~31bf3856ad364e35~amd64~~6.0.1.1 Package registry presence failed, possibly an orphaned package on package watchlist (f) CBS Watchlist Package Missing