Problem Installing SP1 - Windows 7 Home Premium 64 bit

[NoelDP]

Looks like the only current failure is KB2834140 - released in March - as everything else seems to have gone in now.

Let's see what we can find in the SOFTWARE registry hive.


Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should 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:\Windows
hit the enter key - if you get a 'Not Found' error try
DIR D:\Windows
or
DIR E:\Windows


use the drive letter which works in the following command (instead of <drive>)

COPY <drive>:\Windows\System32\config\SOFTWARE <drive>:\SOFTHIVE


run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now zip the C:\SOFTHIVE file (it'll probably be about 100MB!) and post the resulting Zip file to your favourite fileshare site (best are probably Dropbox or SkyDrive), and post a link.
I'll let you know when I have it so you can remove it (there is some sensitive info in it which you don't want getting out too broadly, but should be OK for the limited time here)

I'll have a play and see if I can work out what's wrong and get back to you.

 

[IcecoldUK]

Done!

I've sent you a PM with the dropbox link.

Jon

 

[NoelDP]

Got it - and got it

back later.

 

[IcecoldUK]

Hi Noel,

You said to shout if i hadn't heard anything from you.

Jon

 

[NoelDP]

Thanks for the nudge - I keep forgetting how little time I have nowadays!

You're at the top of the list

 

[IcecoldUK]

No rush mate, except for the windows updates and a few odd little glitches everything appears to be working correctly. I nudged because you asked, and because i didn't want you to think i'd lost interest

Jon

 

[NoelDP]

Looking through the registry, I can't see any of the errors I was expecting - which means (I hope!) that the errors must be in the files.

Please run the following commands, and then zip the created folder up, and upload it

MD %userprofile%\desktop\npfolder
copy c:\windows\servicing\Packages\Package_for_KB2813347~31bf3856ad364e35~amd64~~6.1.1.0.mum %userprofile%\desktop\npfolder
copy c:\windows\servicing\Packages\Package_for_KB2667402~31bf3856ad364e35~amd64~~6.1.2.0.mum %userprofile%\desktop\npfolder
copy c:\windows\servicing\Packages\Package_for_KB2564958~31bf3856ad364e35~amd64~~6.1.1.1.mum %userprofile%\desktop\npfolder
copy c:\windows\servicing\Packages\Package_for_KB2789645~31bf3856ad364e35~amd64~~6.1.1.0.mum %userprofile%\desktop\npfolder

 

[IcecoldUK]

Hi Noel,

I ran the commands as requested, please see attached.

The package for KB2789645 would not copy. I ran the command twice and waited up to 20 minutes, but both times it stalled on KB2789645.

Jon

 

[NoelDP]

That doesn't surprise me too much

Please run a full CHKDSK and then see if the file will copy...



Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

CHKDSK C: /R

and hit the Enter key.
You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, press Enter, and then reboot.

The CHKDSK will take a few hours depending on the size of the drive, so be patient!

After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -

The run another SFC /SCANNOW reboot and post the new CBS.log file.

 

[IcecoldUK]

As requested...

Jon

 

[NoelDP]

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

 

[IcecoldUK]

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

 

[NoelDP]

Here's the full list of error statements from the CBS.log file....

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    [EMAIL="0000018a@2013/9/2:20:07:56.545"]0000018a@2013/9/2:20:07:56.545[/EMAIL] (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    [EMAIL="0000038c@2013/9/2:20:12:22.557"]0000038c@2013/9/2:20:12:22.557[/EMAIL] (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    [EMAIL="00000598@2013/9/2:20:15:43.548"]00000598@2013/9/2:20:15:43.548[/EMAIL] (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    [EMAIL="00000886@2013/9/2:20:22:28.260"]00000886@2013/9/2:20:22:28.260[/EMAIL] (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

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)

I'll have to delve a little deeper and see what the background reveals - back later.

 

[IcecoldUK]

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

 

[IcecoldUK]

Not to worry. I solved the adobe reader issue by installing with IE rather than Firefox. Weird...

Jon

 

[NoelDP]

One reason why I try and avoid Adobe software (I use Foxit Reader - www.foxitsofware.com )

 

[NoelDP]

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

 

[IcecoldUK]

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

 

[IcecoldUK]

*Nudge*

 

[NoelDP]

(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.