How to fix black screen in Windows 7 without copyright

Video How to fix black screen in Windows 7 without copyright

You install pirated Windows and after a few months, the screen goes black and the words " This copy of windows is not genuine" tell your operating system is not Win license. This is an easy fix without downloading the software.

How to fix black screen in Windows 7 without copyright

" This copy of windows is not genuine" error is a common error in the Windows operating system, most commonly on Windows XP, Vista, Windows 7, Windows 8 / 8.1. Many websites instruct you to download a file or software. However, you absolutely have an easier way to fix this problem quickly without using any software.

Note: This tutorial does not convert your operating system from "pirated" to copyrighted Windows but only helps you to use non-copyrighted Windows without errors and updates. If you want full features in the latest version and complete updates, you must purchase the Genuine Operating System from the Microsoft store.

And in case you do not want to spend money and continue to use unlicensed win, this is a fix.

This method is used to fix " This copy of windows is not genuine" error for 32-bit and 64-bit versions of Windows 7. Remember to follow the full 3 steps below. If you have completed step 2 and notice the error is gone and skip step 3, the error may reappear after some time.

Step 1 : Uninstall update KB971033

You get the error " This copy of windows is not genuine ", which means that Windows has an update file that can detect whether your Windows operating system is copyrighted or not. Therefore, before proceeding with the fix, you must remove the update KB971033 that has this detection function.

If you see this update file, uninstall it and if not, skip this step. Follow these steps to turn off the Windows Update function.

  1. Open Control Panel.
  2. Go to the Windows Update section .
  3. Click View Installed Updates
  4. After all the installation updates have finished downloading, look for KB971033 and uninstall.
  5. Reboot the device.

How to fix black screen in Windows 7 without copyright

If you cannot find the update KB971033, you can skip this step and proceed to step 2.

Step 2: Use the SLMGR -REARM command

How to fix black screen in Windows 7 without copyright

  1. Click the Start button to enter the Start Menu.
  2. Type cmd in the search field.
  3. You will see the command prompt option. Right-click on Command Prompt. Select Run as Administrator . Remember, you must run the command as administrator otherwise the command will not work.
  4. A window appears. Type SLMGR -REARM (SLMGR is a Windows software license management tool. REARM is a command to reset the machine's license status). Then press Enter .
  5. You will see a window. Click OK .
  6. Then restart your computer and see the words " This copy of windows is not genuine" has disappeared. However, if you still see this line, try again with the command SLMGR / REARM.

Almost when done, the above command has fixed the black screen error due to unlicensed win. However, in some cases, after completing the above steps, you will be able to receive one of the 2 notifications are:

  • Error " Error 0xc004d307: The maximum allowed the number of rearms has been exceeded ".
  • Or the error " slmgr is not recognized as an internal or external command ".

If this is the case then temporarily skip Step 3 and read down the following to know how to fix it!

Step 3: Turn off automatic Windows updates (Windows Update)

After completing step 2 and see no lines " This copy of windows is not genuine" then proceed to step 3.

You do not use the copyright Windows, so it is not allowed to update. Therefore, turn off the automatic update function of Windows. If not, you will get this error again when Win makes any updates and it detects that the operating system is not genuine.

How to fix black screen in Windows 7 without copyright

  1. Go to Control Panel
  2. Click on Windows Update .
  3. Click Install updates automatically (Recommended)
  4. Select Never Check for Updates (Not recommended)

Everything is done. Now replace the desktop wallpaper with a nice image instead of a black screen!

Fix Error 0xc004d307: The maximum allowed the number of rearms has been exceeded

How to fix black screen in Windows 7 without copyright

You receive this error message when you have tried the SLMGR -REARM command more than 3 times.

There are two ways to fix this error. The first is to reinstall Windows, but it is only a measure to choose the last.

The second way is simpler, just follow these steps:

After using the SLMGR -REARM command 3 times, the registry key (registry key) "SkipRearm" will become "0". You need to change the registration key "SkipRearm" to "1".

You can find "SkipRearm" by visiting the Registry editor under the link HKEY_LOCAL_MACHINE / SOFTWARE / Microsoft / Windows NT / CurrentVersion / SoftwareProtectionPlatform .

Follow the steps below:

  1. Press " Windows + R " and you will see the " Run " dialog box . Or go to Start , select Run .
  2. Type " Regedit ". Click Ok . You will see the Registry editor window.
  3. Click the arrow in the "HKEY_LOCAL_MACHINE" line.
  4. Click the arrow next to "SOFTWARE.
  5. Click the arrow next to "Microsoft".
  6. Click the next arrow in the "Windows NT" line
  7. Click the next arrow in the "CurrentVersion" line.
  8. Click on the words " SoftwareProtectionPlatform " (do not click on the arrow)
  9. Right-click on " SkipRearm " in the right window.
  10. Click " Modify " and change " Value Data " to "1".
  11. Reboot the device.

Now, repeat step 2, use the SLMGR -REARM command to fix black screen errors and lose the words " This copy of windows is not genuine".

Fix the error “Slmgr is not recognized as an internal or external command”

This error may be caused by many reasons.

  • First : It may be because you misspelled the SLMGR -REARM command. Make sure you type correctly, including the space between "SLMGR" and "-REARM".
  • Second : You do not open the Command Prompt as Administrator (administrator).

Solution: Go to Start , type search for " cmd ". Right click on " cmd " and select " Run as Administrator ".

  • Tuesday : The SLMGR -REARM command is not appropriate. Try it with the SLMGR / REARM command .
  • Fourth : Fix by opening Command Prompt as Administrator .
    • Type cd \ and press Enter .
    • Type cd windows \ system32 and press enter .
    • You should now see the line C: \ windows \ system32> . Now use the command like this C: \ windows \ system32> SLMGR -REARM
  • Thursday : The reason the file slmgr.vbs may have any other extensions. You need to remove the extension by renaming the file.

Making:

  1. Go to My Computer .
  2. On the C drive .
  3. Select the Windows folder .
  4. Select the folder " System32 ".
  5. Go down until you see " slmgr.vbs.REMOVEWAT ". Right-click on it and rename it to "slmgr.vbs." If you can't find the "REMOVEWAT" extension, delete any other extensions with redundancies after the word "slmgr.vbs".

Summary

In case all of the above steps still fail, reinstall Windows. Take each step carefully so you don't have to see this error again.

When following the above steps do not see any errors. You can use this operating system forever without updating.

However, viruses and malware always attack operating system versions and software on the computer if the operating system is outdated. So, if possible, use the latest operating system and application version.

Hope you are succesful.

Leave a Comment

Put Collabora Behind Nginx Without Breaking WebSockets

Put Collabora Behind Nginx Without Breaking WebSockets

Configure Nginx TLS termination, Collabora routes, and WebSocket headers, then test the public endpoints before opening real documents.

Stop CODE Editing Sessions from Ending at 10 Minutes

Stop CODE Editing Sessions from Ending at 10 Minutes

Trace a 10-minute CODE disconnect to its proxy, load balancer, or WebSocket path, then correct the timeout and verify the session stays connected.

Deploy Collabora CODE on Kubernetes with Helm

Deploy Collabora CODE on Kubernetes with Helm

Install the official Collabora Helm chart, configure WOPI access and ingress affinity, and verify the deployment without common setup mistakes.

Trace a Blank Collabora Document to the Failing Layer

Trace a Blank Collabora Document to the Failing Layer

Use browser requests, WOPI logs, and targeted proxy checks to find why Collabora opens a blank document—and choose a fix that fits the evidence.

Enable Multilingual Spell Check in Collabora Online CODE

Enable Multilingual Spell Check in Collabora Online CODE

Configure CODE Docker dictionaries and tag document passages correctly so English, French, and other supported languages receive the right spell-checking.

Set Collabora’s Idle Timer for Active Document Views

Set Collabora’s Idle Timer for Active Document Views

Adjust the per-view inactivity threshold in coolwsd and distinguish it from background-tab dimming, document unloading, autosave, and login expiration.

Disable Collabora CODE Update Checks and Unwanted Connections

Disable Collabora CODE Update Checks and Unwanted Connections

Stop scheduled CODE update checks, review optional remote services, and use outbound network controls without breaking document editing.

Connect Seafile and Collabora with the Correct WOPI URL

Connect Seafile and Collabora with the Correct WOPI URL

Enable secure document editing in Seafile by configuring Collabora’s discovery URL, HTTPS, and WOPI access for your deployment.

Restore Copy and Paste Between Collabora and Desktop Apps

Restore Copy and Paste Between Collabora and Desktop Apps

Test the system clipboard, adjust browser permissions, and identify when an embedded Collabora integration needs an iframe policy change.

Make Custom Fonts Available in Collabora CODE Docker

Make Custom Fonts Available in Collabora CODE Docker

Mount font files into Docker and Collabora’s systemplate so custom typefaces appear in the editor and render correctly in documents.