Computer won't boot after replacing imageres.dll and shell32.dll

Page 2 of 2 FirstFirst 12

  1. Posts : 2,799
    Linux Mint 20.1 Win10Prox64
       #11

    For newer model of HP. Try F9 or F10
      My Computer


  2. Posts : 12,801
    Windows 11 Pro
       #12

    I've wondered why they even put Manuals out anymore. Most of them, you could put the useful information on 1 page. Asus, in it's infinite wisdom, decided to make F8 the one time boot menu hotkey. Starting in safe mode when you can't boot is a real trick sometimes. Of all the F keys, why choose that one?
      My Computer


  3. Posts : 27,183
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #13

    essenbe said:
    I've wondered why they even put Manuals out anymore. Most of them, you could put the useful information on 1 page. Asus, in it's infinite wisdom, decided to make F8 the one time boot menu hotkey. Starting in safe mode when you can't boot is a real trick sometimes. Of all the F keys, why choose that one?
    Maybe someone should put forth a resolution, that there be a Recovery Standard industry wide, to their local Computer Geek political parties(like the Pirate Party in European countries which is also in the EU Parliament).
      My Computers


  4. Posts : 12,801
    Windows 11 Pro
       #14

    I thought the OEMs and Component manufacturers were already Pirates.
      My Computer


  5. Posts : 5
    Windows 10 Home
    Thread Starter
       #15

    THANK YOU GUYS SO MUCH!!!!! I was finally able to restore my backups, and now my computer's working again. Thank you!!!! Can anyone tell me how to properly replace imageres.dll and shell32.dll?
      My Computer


  6. Posts : 27,183
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #16

    You need to take ownership(tutorial and download here) and change the name from .dll to old(never delete in case something doesn't go right) then swap place the new ones in system32 and SySWOW64(best to keep the original copies in Documents and copy to their respective places) Yes they both must be done, they have a 32 bit and a 64bit version, and be careful not to mix them up. It's best & safest to make separate folders in Documents when importing the new dll files one sys32 and one syswow64.

    So in short:
    1. VERY IMPORTANT: CREATE A SYSTEM IMAGE BEFORE HAND!!! You can use Macrium Reflect free if you don't have an imager. Do not trust a restore point(ever ever ever). Until you have an image and know you can boot into the recovery environment-Do not touch system files with a stick even.
    2. take ownership
    3. change name to .old
    4. copy new files to respective folders
    5. try just signing out then back in first, if that doesn't do it re boot.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:41.
Find Us




Windows 10 Forums