New
#71
There's three background errors in the SFC san which I don't fully understand - please try running the CheckSUR scan again, and post just the CheckSUR.log file
There's three background errors in the SFC san which I don't fully understand - please try running the CheckSUR scan again, and post just the CheckSUR.log file
Would you mind if i asked what errors you have found, as i'd like to try and understand what's happening.
CheckSUR attached.
Jon
Here's the full list of error statements from the CBS.log file....
They indicate problems with a couple of the manifest files - but these haven't been pick up by the CheckSUR tool (your log is clear)Code:Line 2644: 2013-09-02 17:34:31, Error CBS Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM] Line 2646: 2013-09-02 17:34:31, Error CBS Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM] Line 5635: 2013-09-02 17:34:34, Error CBS Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM] Line 5637: 2013-09-02 17:34:34, Error CBS Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM] Line 5704: 2013-09-02 17:34:35, Error CBS Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM] Line 5706: 2013-09-02 17:34:35, Error CBS Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM] Line 37055: 2013-09-02 17:35:07, Error CBS Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED] Line 46269: 2013-09-02 21:07:56, Error CSI 0000018a@2013/9/2:20:07:56.545 (F) d:\win7sp1_gdr\base\xml\udom_microdom.cpp(3734): Error c000003e [Error,Facility=(system),Code=62 (0x003e)] originated in function MicrodomImplementation::CDomLayoutCache::AdvanceCachedPointer expression: (ulElementType == (0x2)) || (ulElementType == (0x3)) || (ulElementType == (0x5)) || (ulElementType == (0x1)) || (ulElementType == (0x6)) || (ulElementType == (0x7)) || (ulElementType == (0x4)) Line 48697: 2013-09-02 21:12:22, Error CSI 0000038c@2013/9/2:20:12:22.557 (F) d:\win7sp1_gdr\base\xml\udom_microdom.cpp(3734): Error c000003e [Error,Facility=(system),Code=62 (0x003e)] originated in function MicrodomImplementation::CDomLayoutCache::AdvanceCachedPointer expression: (ulElementType == (0x2)) || (ulElementType == (0x3)) || (ulElementType == (0x5)) || (ulElementType == (0x1)) || (ulElementType == (0x6)) || (ulElementType == (0x7)) || (ulElementType == (0x4)) Line 51173: 2013-09-02 21:15:43, Error CSI 00000598@2013/9/2:20:15:43.548 (F) d:\win7sp1_gdr\base\xml\udom_microdom.cpp(4111): Error STATUS_INVALID_PARAMETER originated in function MicrodomImplementation::CStringpoolCache::FindString expression: StringId < m_Entries.Length Line 54675: 2013-09-02 21:22:28, Error CSI 00000886@2013/9/2:20:22:28.260 (F) d:\win7sp1_gdr\base\xml\udom_microdom.cpp(4111): Error STATUS_INVALID_PARAMETER originated in function MicrodomImplementation::CStringpoolCache::FindString expression: StringId < m_Entries.Length
I'll have to delve a little deeper and see what the background reveals - back later.
Hi Noel,
I just come across an error while reinstalling Adobe Reader (see attached).
Do you think this could be related to the issues we are having or should i search for a separate solution?
Jon
Not to worry. I solved the adobe reader issue by installing with IE rather than Firefox. Weird...
Jon
One reason why I try and avoid Adobe software :) (I use Foxit Reader - www.foxitsofware.com )
I *hope* this is right! :)
Please compress the following files to a folder, and post the resulting file..
C:\Windows\winsxs\Manifests\wow64_microsoft-windows-t..minalservicesclient_31bf3856ad364e35_6.1.7600.21448_none_b4ddb01f8823ee4c.manifest
C:\Windows\winsxs\Manifests\wow64_microsoft-windows-t..minalservicesclient_31bf3856ad364e35_6.1.7601.22252_none_b6b33b7d8557de1f.manifest
C:\Windows\servicing\Packages\package_for_kb2813347~31bf3856ad364e35~amd64~~6.1.1.0.mum
Hi Noel, please see the attached.
Please note that i could not find the file for wow64_microsoft-windows-t..minalservicesclient_31bf3856ad364e35_6.1.7600.21448_none_b4ddb01f8823ee4c.manifest
Jon
(I hadn't forgotten you :))
I wonder if it's worth replacing that 'missing' file? It shouldn't cause problems, I don't think - even if it's not appropriate.
The other files appear to be OK.
I've uploaded a file - iukaazip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print theseinstructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, starttapping F8 - this should bring up the Advanced Boot Menu, at the top of whichshould be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\iukaa
hit the enter key - if you get a 'NotFound' error try
DIR D:\iukaa
or
DIR E:\iukaa
The drive letter in use when you find the folder willneed to be substituted (for<drive>) into the followingcommand...
XCOPY<drive>:\iukaa <drive>:\windows\winsxs\Manifests /y /i /s /v /h
(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )
run the command (it should take almost no time)andwhen the prompt returns, type
EXIT
and hit the Enter key to exit CommandPrompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in anElevated Command Prompt
then reboot and upload the new CBS.log
then run another CheckSUR scan, and post the new log - and we'll see what's happened.