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

Page 1 of 2 12 LastLast

  1. Posts : 461
    Win 10 Pro x64, Win 7 Pro x64
       #1

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


    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...
    Last edited by Urthboundmisfit; 29 Apr 2014 at 04:49. Reason: add link to 7 tutorial; clarity
      My Computer


  2. Posts : 1,346
    Windows 7 Professional x64
       #2

    Urthboundmisfit said:
    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;

    Elevated Command Prompt

    HTH
      My Computer


  3. Posts : 461
    Win 10 Pro x64, Win 7 Pro x64
    Thread Starter
       #3

    Sir George said:
    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

    Attachment 315823

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

    Attachment 315827

    Further thoughts, ideas?


    Last edited by Urthboundmisfit; 02 May 2014 at 05:36.
      My Computer


  4. Posts : 72,012
    64-bit Windows 11 Pro for Workstations
       #4

    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.

    SFC /SCANNOW Command - System File Checker

    Hope this helps, :)
    Shawn
    Last edited by Brink; 29 Apr 2014 at 09:08. Reason: typo
      My Computer


  5. Posts : 1,346
    Windows 7 Professional x64
       #5

    Urthboundmisfit said:
    Sir George said:
    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

    Attachment 315823

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

    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.
      My Computer


  6. Posts : 461
    Win 10 Pro x64, Win 7 Pro x64
    Thread Starter
       #6

    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:)
    Last edited by Urthboundmisfit; 29 Apr 2014 at 08:58. Reason: add copy info
      My Computer


  7. Posts : 1,346
    Windows 7 Professional x64
       #7

    Urthboundmisfit said:
    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.
      My Computer


  8. Posts : 461
    Win 10 Pro x64, Win 7 Pro x64
    Thread Starter
       #8

    Sir George said:
    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)
    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!
    Last edited by Urthboundmisfit; 02 May 2014 at 05:36.
      My Computer


  9. Posts : 461
    Win 10 Pro x64, Win 7 Pro x64
    Thread Starter
       #9

    Brink said:
    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.

    SFC /SCANNOW Command - System File Checker

    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.



    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. :)
    Last edited by Urthboundmisfit; 29 Apr 2014 at 18:48. Reason: clarity
      My Computer


  10. Posts : 72,012
    64-bit Windows 11 Pro for Workstations
       #10

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


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 01:22.
Find Us