Tag Archives: fixes

How to remove ‘SecureBoot isn’t configured correctly’ watermark on Windows 8.1

The ‘SecureBoot isn’t configured correctly’ watermark in question is this:

This guide will remove the watermark by replacing all text with invisible spaces, using a tried and tested method that has been used in earlier Windows versions to remove similar watermarks.

Don’t follow this guide unless you have exhausted all the other options, such as group policy, clearing keys and otherwise fidding with BIOS options. I’m one of the unlucky ones that has a BIOS with UEFI support but no SecureBoot options at all, so this was my only choice.

 

  1. Install Resource Hacker
  2. Install TakeOwnership
  3. Install Process Hacker
  4. Open C:\Windows\Branding\Basebrd\en-GB\basebrd.dll.mui with Resource Hacker (en-US if American)
  5. Go to String Table > 1 > 2057 and replace the contents of strings 12 and 13 with a space, e.g.:
    12,     " "
  6. Click ‘Compile Script’ then File>Save As and save with the same name but to a different folder (e.g. your desktop)
  7. Right click C:\Windows\Branding\Basebrd\en-GB\basebrd.dll.mui, and select Take Ownership, then delete it and copy the one from your desktop into its place
  8. Open C:\Windows\System32\en-GB\shell32.dll.mui with Resource Hacker (en-US if American)
  9. Go to String Table > 2070 > 2057 and do the same process as above with strings 33108, 33115 and 33117
  10. Click ‘Compile Script’ then File>Save As and save with the same name but to a different folder (e.g. your desktop)
  11. Open Process Hacker and click the ‘Find Handles or DLLs’ button in the main toolbar
  12. In the search box type ‘shell32.mui.dll’ and click ‘Find’
  13. Order the results by the ‘Type’ column
  14. Select all results of type ‘File’ by shift-clicking, ignoring the ones of  type ‘Mapped File’
  15. Right click and choose ‘close’, accepting any warnings
  16. Close Process Hacker
  17. Right click C:\Windows\System32\en-GB\shell32.dll.mui, and select Take Ownership, then delete it and copy the one from your desktop into its place
  18. Reboot

Fix for Samsung 750 and 950 series monitors 120Hz “Not Optimum Mode”

Use 120.8Hz custom refresh rate. Both Windows and the monitor’s OSD will show 121Hz. Actual 121.0Hz will cause the error without fail, it must be a tiny bit below. I guess there is something weird going on with the tolerances in the monitor – I’ve noticed things like mains current spikes contribute to the problem.

This may apply more to HDMI 1440×1080 or 1280×720 than to DisplayPort 1080p.

My exact settings for 1440x1080x120Hz over HDMI are as follows: