Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: Problem Installing SP1 - Windows 7 Home Premium 64 bit

11 Sep 2013   #81

Windows 7 64 bit Home Premium
 
 

Hi Noel,

The new manifest file has been added.

CBS & SURT logs attached. I had to re-run the SFC several times due to "Windows Resource Protection"

Jon



Attached Files
File Type: zip CBS.zip (5.54 MB, 1 views)
My System SpecsSystem Spec
.

11 Sep 2013   #82

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

I'm having problem s working out what the errors in the current CBS log actually mean...
Having said that, there are a couple of very obvious errors in the SFC scan - but I can't work out to which file they relate!
Code:
2013-09-11 19:07:07, Error                 CSI    00000718 (F) Manifest parsing failed:
    Status: STATUS_UNSUCCESSFUL
    Node: 41722 (0x0000a2fa)
    Node (ln 10071 col 18) xpath: /#document/assembly/registryKeys/registryKey/@keyName
    Strings: ([ml:67,l67]"HKEY_CLASSES_RMOT\Interface\{F98BCE04-4A4B-398C-A512-FD8348D51E3B}\")[gle=0x80004005]
2013-09-11 19:07:07, Error                 CSI    00000719@2013/9/11:18:07:07.455 (F) d:\win7sp1_gdr\base\wcp\manifestparser\pcmc_manifestwalker.cpp(5009): Error STATUS_UNSUCCESSFUL originated in function CMicrodomManifestWalker::CommonReportError expression: (null)
Code:
2013-09-11 19:05:32, Error                 CSI    00000640 (F) Manifest parsing failed:
    Status: STATUS_UNSUCCESSFUL
    Node: 1449 (0x000005a9)
    Node (ln 345 col 18) xpath: /#document/assembly/registryKeys/registryKey/@keyName
    Strings: ([ml:74,l74]"HKEY_CLASSES_RMOT\Interface\{B05651AF-9B10-425E-B616-1FCD828DB3B1}\TypeLib")[gle=0x80004005]
2013-09-11 19:05:32, Error                 CSI    00000641@2013/9/11:18:05:32.685 (F) d:\win7sp1_gdr\base\wcp\manifestparser\pcmc_manifestwalker.cpp(5009): Error STATUS_UNSUCCESSFUL originated in function CMicrodomManifestWalker::CommonReportError expression: (null)
[gle=0x80004005]
2013-09-11 19:05:32, Info                  CSI    00000642 [SR] Cannot verify component files for WindowsSearchEngine, Version = 7.0.7601.17610, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
There are very obvious bitflips in there

One of the files involved may be
wow64_windowssearchengine_31bf3856ad364e35_7.0.7601.17610_none_dbd0d3376679543d.manifest
but I can't find the other file ref anywhere.


There are another three failure points...
Code:
 Line 687: 2013-09-11 18:48:28, Error                 CSI    000000b4@2013/9/11:17:48:28.058 (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 2953: 2013-09-11 18:52:51, Error                 CSI    000002a1@2013/9/11:17:52:51.246 (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 4929: 2013-09-11 19:00:41, Error                 CSI    0000042b@2013/9/11:18:00:41.932 (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))
- which I have no idea what they mean

I think at this point, the only realistic thing I can offer is a repair install
My System SpecsSystem Spec
12 Sep 2013   #83

Windows 7 64 bit Home Premium
 
 

Hi Noel,

I tried the repair install as you suggested but I received the attached error message. I've tried repair installs previously all of which failed which is why I did the clean install.

Could it be a service running in the background preventing the repair and the windows updates?

I'm totally out of ideas myself, so if you have any colleges you could ask to jump in for advice it'd be appreciated.

What are the chances of these issues being related to a hardware/driver problem?

Jon


Attached Images
 
My System SpecsSystem Spec
.


12 Sep 2013   #84

Windows 7 64 bit Home Premium
 
 

What's the chances it could be a windows resource protection problem? Would it be worth disabling it and re-running SFC?
My System SpecsSystem Spec
12 Sep 2013   #85

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

SFC uses Windows Resource Protection in its assessment - so shutting it down would prevent SFC from functioning.
My System SpecsSystem Spec
12 Sep 2013   #86

Windows 7 64 bit Home Premium
 
 

Ah i see....

Noel, would you mind taking a look at the new attached CBS log when you get a moment to see if those same errors are still present please.


Attached Files
File Type: zip CBS.zip (6.28 MB, 1 views)
My System SpecsSystem Spec
13 Sep 2013   #87

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

There are a fiar number of manifest file problems....
Code:
Line 128: 2013-09-12 11:56:00, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 130: 2013-09-12 11:56:00, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 149: 2013-09-12 11:56:00, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 151: 2013-09-12 11:56:00, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 162: 2013-09-12 11:56:00, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 164: 2013-09-12 11:56:00, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 403: 2013-09-12 11:56:01, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 405: 2013-09-12 11:56:01, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 433: 2013-09-12 11:56:01, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 435: 2013-09-12 11:56:01, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 453: 2013-09-12 11:56:01, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 455: 2013-09-12 11:56:01, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 474: 2013-09-12 11:56:01, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 476: 2013-09-12 11:56:01, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 819: 2013-09-12 11:56:02, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 821: 2013-09-12 11:56:02, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 832: 2013-09-12 11:56:02, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 834: 2013-09-12 11:56:02, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 851: 2013-09-12 11:56:03, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 853: 2013-09-12 11:56:03, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 874: 2013-09-12 11:56:03, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 876: 2013-09-12 11:56:03, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 893: 2013-09-12 11:56:03, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 895: 2013-09-12 11:56:03, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 1798: 2013-09-12 11:56:04, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 50311: 2013-09-12 15:27:18, Error                 CSI    00000322 (F) Manifest parsing failed:
 Line 50316: 2013-09-12 15:27:18, Error                 CSI    00000323@2013/9/12:14:27:18.922 (F) d:\win7sp1_gdr\base\wcp\manifestparser\pcmc_manifestwalker.cpp(5009): Error STATUS_UNSUCCESSFUL originated in function CMicrodomManifestWalker::CommonReportError expression: (null)
 Line 51440: 2013-09-12 16:28:39, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 51442: 2013-09-12 16:28:39, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 51457: 2013-09-12 16:28:40, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 51459: 2013-09-12 16:28:40, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 51975: 2013-09-12 16:28:40, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 51977: 2013-09-12 16:28:40, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 52018: 2013-09-12 16:28:40, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 52020: 2013-09-12 16:28:40, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 52033: 2013-09-12 16:28:40, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 52035: 2013-09-12 16:28:40, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 52054: 2013-09-12 16:28:40, Error                 CBS    Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 52056: 2013-09-12 16:28:40, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
 Line 57340: 2013-09-12 16:37:29, Error                 CSI    000001f5@2013/9/12:15:37:29.977 (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))
...and a larger number of other problems (which may be a result of the manifest ones)

The following error is still there..
Code:
2013-09-12 15:27:18, Error                 CSI    00000322 (F) Manifest parsing failed:
    Status: STATUS_UNSUCCESSFUL
    Node: 14790 (0x000039c6)
    Node (ln 3571 col 5) xpath: /#document/assembly/registryKeys/registryKey
    Strings: ([ml:8,l7]"keyName", [ml:0]"", [ml:33,l32]"urn:schemas-microsoft-com:asm.v1", [ml:33,l32]"urn:schemas-microsoft-com:asm.v2", [ml:33,l32]"urn:schemas-microsoft-com:asm.v3")[gle=0x80004005]
2013-09-12 15:27:18, Error                 CSI    00000323@2013/9/12:14:27:18.922 (F) d:\win7sp1_gdr\base\wcp\manifestparser\pcmc_manifestwalker.cpp(5009): Error STATUS_UNSUCCESSFUL originated in function CMicrodomManifestWalker::CommonReportError expression: (null)
[gle=0x80004005]
My System SpecsSystem Spec
13 Sep 2013   #88

Windows 7 64 bit Home Premium
 
 

Damn!

Any ideas what could be causing it, or how we should proceed?

Jon
My System SpecsSystem Spec
14 Sep 2013   #89

Windows 7 64 bit Home Premium
 
 

Ive just noticed from the errors you posted that there are 2 instances which point to "d:\win7sp1_gdr\base" which is my DVD-ROM drive. Is that normal considering the Win 7 disc is not in the drive?

I'm just clutching at straws here now...

Jon
My System SpecsSystem Spec
14 Sep 2013   #90

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

It's normal - in these cases the drive is actually a virtual one, I think
My System SpecsSystem Spec
Reply

 Problem Installing SP1 - Windows 7 Home Premium 64 bit





Thread Tools



Similar help and support threads for2: Problem Installing SP1 - Windows 7 Home Premium 64 bit
Thread Forum
Windows 7 Home Premium x64 Genuine Problem Windows Updates & Activation
Internet not working after re-installing windows 7 home premium Drivers
Asking for username/password while installing Windows 7 Home Premium Installation & Setup
Solved Installing new Windows 7 Home Premium in English, with german copy Installation & Setup
Installing institution-avail Windows Professional over Home Premium Installation & Setup
Installing Windows 7 over Vista home Premium Installation & Setup

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:10 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33