Solved Need help Re:sfc /scannow cannot repair shellbrd.dll

[Urthboundmisfit]

Hello 7 gurus I'm a n00b that needs help regarding these entries in SFC log:

2014-04-29 03:13:51, Info CSI 0000003d [SR] Cannot repair member file [l:24{12}]"shellbrd.dll" of Microsoft-Windows-Branding-Shell-HomePremium, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2014-04-29 03:13:51, Info CSI 0000003f [SR] Cannot repair member file [l:24{12}]"shellbrd.dll" of Microsoft-Windows-Branding-Shell-HomePremium, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2014-04-29 03:13:51, Info CSI 00000040 [SR] This component was referenced by [l:214{107}]"Microsoft-Windows-Branding-HomePremium-Client-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.BHPC Namespace"
2014-04-29 03:13:51, Info CSI 00000043 [SR] Could not reproject corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\Branding\Shellbrd"\[l:24{12}]"shellbrd.dll"; source file in store is also corrupted.

I recently "fooled around" with changing the OEM Information on System properties page in W7 HomePrem SP1 x64 using instrux from this guide (and others floating around the Netz) and decided to change everything back to it's previous (original) state. After doing so I ran SFC /SCANNOW and discovered the above errors.

Please advise how to replace/repair the file(s), I have repair/install DVD's & USB media as well as several install ISO's on my local drive and a test 7 installation in VMWare that I can copy file(s) from, however this I'm afraid is above my pay grade lol. I need instrux with permissions (if needed), reg files, register/unregister dll's, etc...

 

[Sir George]

Hello 7 gurus I'm a n00b that needs help regarding these entries in SFC log:

2014-04-29 03:13:51, Info CSI 0000003d [SR] Cannot repair member file [l:24{12}]"shellbrd.dll" of Microsoft-Windows-Branding-Shell-HomePremium, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2014-04-29 03:13:51, Info CSI 0000003f [SR] Cannot repair member file [l:24{12}]"shellbrd.dll" of Microsoft-Windows-Branding-Shell-HomePremium, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2014-04-29 03:13:51, Info CSI 00000040 [SR] This component was referenced by [l:214{107}]"Microsoft-Windows-Branding-HomePremium-Client-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.BHPC Namespace"
2014-04-29 03:13:51, Info CSI 00000043 [SR] Could not reproject corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\Branding\Shellbrd"\[l:24{12}]"shellbrd.dll"; source file in store is also corrupted.

I recently "fooled around" with changing the OEM Information on System properties page in W7 HomePrem SP1 x64 using instrux from this guide (and others floating around the Netz) and decided to change everything back to it's previous (original) state. After doing so I ran SFC /SCANNOW and discovered the above errors.

Please advise how to replace/repair the file(s), I have repair/install DVD's & USB media as well as several install ISO's on my local drive and a test 7 installation in VMWare that I can copy file(s) from, however this I'm afraid is above my pay grade lol. I need instrux with permissions (if needed), reg files, register/unregister dll's, etc...

Try;

1. Retrieve shellbrd.dll from your system setup disk, another PC running the same system as yours, or through DLL Suite database.
2. Save shellbrd.dll to C:WindowsSystem32BrandingShellBrd
3. Type regsvr32 shellbrd.dll and press Enter in CMD window

See the following for how to use an elevated CMD in Windows 7 referenced in item #3;

http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html

HTH

 

[Urthboundmisfit]

Try;
1. Retrieve shellbrd.dll from your system setup disk, another PC running the same system as yours, or through DLL Suite database.
2. Save shellbrd.dll to C:WindowsSystem32BrandingShellBrd
3. Type regsvr32 shellbrd.dll and press Enter in CMD window

HTH

TY for the reply/suggestion but unfortunately it didn't work

View attachment 315823

Tried Elevated "Open Here" cmd in C:Windows-System32-Branding & had semi success (I think?):

View attachment 315827

Further thoughts, ideas?

 

[Brink]

Hello Urthboundmisfit,

In addition, you might see if the items listed in the note box under step 4 in OPTION TWO of the tutorial below may be able to allow SFC to repair the files afterwards.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Hope this helps,
Shawn

 

[Sir George]

Try;
1. Retrieve shellbrd.dll from your system setup disk, another PC running the same system as yours, or through DLL Suite database.
2. Save shellbrd.dll to C:WindowsSystem32BrandingShellBrd
3. Type regsvr32 shellbrd.dll and press Enter in CMD window

HTH

TY for the reply/suggestion but unfortunately it didn't work

View attachment 315823

Tried Elevated "Open Here" cmd in C:Windows-System32-Branding & had semi success (I think?):

View attachment 315827

Further thoughts, ideas?

Try rebooting the system and see if that corrects the problem. If it doesn't work, you may have copied a different version of shellbrd.dll. Where did you get the file? Are you using the same version of Windows, 32Bit / 64Bit?

Post back your results.

 

[Urthboundmisfit]

Great minds think alike, I rebooted and ran the regsvr elevated cmd as before, same result.
ETA: Copied shellbrd.dll from my Virtual 7 install, same version x64 Home Prem.

@Shawn: TY for the suggestion, will try now & post back results

 

[Sir George]

Great minds think alike, I rebooted and ran the regsvr elevated cmd as before, same result.
ETA: Copied shellbrd.dll from my Virtual 7 install, same version x64 Home Prem.

@Shawn: TY for the suggestion, will try now & post back results

If Shawn's suggestion fails to correct the problem, do a search for the file and see if there is more than 1 copy on your system.

 

[Urthboundmisfit]

If Shawn's suggestion fails to correct the problem, do a search for the file and see if there is more than 1 copy on your system.

...Still processing Shawn's suggestions- 3 sfc scans, same results.

Search for shellbrd.dll results in 1 copy only (I believe I deleted the SXS copies after sfc said they were corrupt & failed)
View attachment 315835

Ran SURT & Chksur log shows packages as missing:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 23.0
2014-04-29 10:20

Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages

Checking Component Store
(f) CSI Payload File Missing 0x00000000 shellbrd.dll amd64_microsoft-windows-b..g-shell-homepremium_31bf3856ad364e35_6.1.7600.16385_none_9c05526173da9e18
(f) CSI Payload File Missing 0x00000000 shellbrd.dll amd64_microsoft-windows-b..-shell-professional_31bf3856ad364e35_6.1.7600.16385_none_02f2d0326102c1bf
(f) CSI Payload File Missing 0x00000000 shellbrd.dll amd64_microsoft-windows-b..ding-shell-ultimate_31bf3856ad364e35_6.1.7600.16385_none_209493e8e411a4e5

Summary:
Seconds executed: 104
Found 3 errors
CSI Payload File Missing Total count: 3

Dism /online /Get-Packages>featurelist.txt confirms missing packages... I am somewhat familiar with DISM, how would I find then add these 3 missing packages?

Thank you again guys for your excellent support!

 

[Urthboundmisfit]

Hello Urthboundmisfit,

In addition, you might see if the items listed in the note box under step 4 in OPTION TWO of the tutorial below may be able to allow SFC to repair the files afterwards.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Hope this helps,
Shawn

• If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 or more times to completely fix everything that it's able to.

Done, no change.

• If not, then download and run the 32-bit (x86) or 64-bit (x64) System Update Readiness Tool for your same installed 32-bit or 64-bit Windows 7, restart the PC afterwards, and try the sfc /scannow command again.

Done, SURT noted packages missing but did not/could not repair.

• If still not, then try using OPTION ONE above to run the sfc /scannow command at boot.

Done, no change.

• If still not, then you can attempt to run a System Restore using a restore point dated before the bad file occured to fix it. You may need to repeat doing a System Restore until you find a older restore point that may work.

No can do, Sys Restore is turned off (small SSD drive). No backups (I know, I know...blushes)

• If still not, then you can use the steps in the TIP box in the OPTION THREE section below to manually replace the files that SFC could not fix if there are not to many fix.

Done extracted shellbrd.dll from install.wim (Index 2, Home Premium) on DVD, same result when running regsvr.

If you would like to get help with your SFC issue, then be sure to post including your sfcdetails.txt file from OPTION THREE below.

That's why I'm here.

 

[Brink]

In that case, you might consider a repair install if what George posted doesn't work either.

 

[Urthboundmisfit]

In that case, you might consider a repair install if what George posted doesn't work either.

Hi Shawn... at this point repair install seems in order... it shouldn't be too painful as I have an up-to-date (Post SP1 updates thru today) & mostly tweaked (services, sound themes, etc) USB install media & all device drivers saved to DVD's & USB stick & most of my data, & stuff backed up to OneDrive, Mediafire, Google Drive, USB's etc.

Will a repair install affect installed programs? I'm mostly concerned about my printer, I had a hard enough time setting it up the first time. Is there a config file I can save somewhere? Printer is Epson XP-410 "Small" In One.

 

[Sir George]

In that case, you might consider a repair install if what George posted doesn't work either.

Hi Shawn... at this point repair install seems in order... it shouldn't be too painful as I have an up-to-date (Post SP1 updates thru today) & mostly tweaked (services, sound themes, etc) USB install media & all device drivers saved to DVD's & USB stick & most of my data, & stuff backed up to OneDrive, Mediafire, Google Drive, USB's etc.

Will a repair install affect installed programs? I'm mostly concerned about my printer, I had a hard enough time setting it up the first time. Is there a config file I can save somewhere? Printer is Epson XP-410 "Small" In One.

The link below should help answer your question(s);

http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[Urthboundmisfit]

Smooth as silk...

Just finished repair install (went swimmingly), problem solved!

Ran sfc and strangely enough it found 2 errors, which it repaired on reboot:

2014-04-29 19:13:28, Info CSI 00000445 [SR] Repairing corrupted file [ml:520{260},l:48{24}]"\??\C:\Windows\Boot\PCAT"\[l:14{7}]"bootmgr" from store
2014-04-29 19:13:28, Info CSI 00000446 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\Resources\Themes"\[l:24{12}]"nature.theme" from store
2014-04-29 19:13:28, Info CSI 00000448 [SR] Repair complete
2014-04-29 19:13:28, Info CSI 00000449 [SR] Committing transaction
2014-04-29 19:13:28, Info CSI 0000044a [SR] Cannot commit interactively, there are boot critical components being repaired
2014-04-29 19:13:28, Info CSI 0000044b [SR] Repairing 2 components
2014-04-29 19:13:28, Info CSI 0000044c [SR] Beginning Verify and Repair transaction
2014-04-29 19:13:28, Info CSI 0000044e [SR] Repairing corrupted file [ml:520{260},l:48{24}]"\??\C:\Windows\Boot\PCAT"\[l:14{7}]"bootmgr" from store
2014-04-29 19:13:28, Info CSI 0000044f [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\Resources\Themes"\[l:24{12}]"nature.theme" from store
2014-04-29 19:13:28, Info CSI 00000451 [SR] Repair complete

As for the actual repair install, all post SP1 updates were successfully integrated except 3 -- 2 of which cannot be integrated + April's MSRT:

Only "problem" I came across so far is font format changed... I probably forgot to tweak it in WinToolkit.

Thanks again guys for the excellent support, it's what makes this site one of the two best puter support sites (along with Bleepingcomputer) on the "Tangled up InnerTubes" today!

 

[Brink]

Great news. I'm glad it was able to help.

 

[Sir George]

Just finished repair install (went swimmingly), problem solved!

Ran sfc and strangely enough it found 2 errors, which it repaired on reboot:

2014-04-29 19:13:28, Info CSI 00000445 [SR] Repairing corrupted file [ml:520{260},l:48{24}]"\??\C:\Windows\Boot\PCAT"\[l:14{7}]"bootmgr" from store
2014-04-29 19:13:28, Info CSI 00000446 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\Resources\Themes"\[l:24{12}]"nature.theme" from store
2014-04-29 19:13:28, Info CSI 00000448 [SR] Repair complete
2014-04-29 19:13:28, Info CSI 00000449 [SR] Committing transaction
2014-04-29 19:13:28, Info CSI 0000044a [SR] Cannot commit interactively, there are boot critical components being repaired
2014-04-29 19:13:28, Info CSI 0000044b [SR] Repairing 2 components
2014-04-29 19:13:28, Info CSI 0000044c [SR] Beginning Verify and Repair transaction
2014-04-29 19:13:28, Info CSI 0000044e [SR] Repairing corrupted file [ml:520{260},l:48{24}]"\??\C:\Windows\Boot\PCAT"\[l:14{7}]"bootmgr" from store
2014-04-29 19:13:28, Info CSI 0000044f [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\Resources\Themes"\[l:24{12}]"nature.theme" from store
2014-04-29 19:13:28, Info CSI 00000451 [SR] Repair complete

As for the actual repair install, all post SP1 updates were successfully integrated (except the 3 pictured below) 2 of which cannot be integrated + April's MSRT:

View attachment 315894

Only "problem" I came across so far is font format changed... I probably forgot to tweak it in WinToolkit.

Thanks again guys for the excellent support, it's what makes this site one of the two best puter support sites (along with Bleepingcomputer) on the "Tangled up InnerTubes" today!

Great!

 

[Urthboundmisfit]

Discovered problems in Event Viewer with VMWare Player (Network) & Avast (dunno??)... Repair installs of both progs should fix them... key word being should. :sarc:

Stay tuned, kiddies!

 

[Brink]

Fingers crossed.

 

[Urthboundmisfit]

All is well in UBM land... repair installs of VMWare & Avast, several reboots & my event viewer is clean as a whistle.

Thanks again guys!