If you are not authorized to activate your version of Windows and you encounter activation error 0xc004f063, you can read this message on Techquack. It will show you some viable methods to solve this problem. We hope you find this post useful.
You may not be able to activate your Windows build. The error code that occurs when this process fails is 0xc004f063, and the error code is always accompanied by the error message “Software licensing service has reported that the computer BIOS lacks the required license”.
This problem is most common in Windows 7, but also in Windows 8.1 and Windows 10. What is the cause of the activation error 0xc004f063? Here are several possible causes: license limitation, BIOS mismatch, corrupted system files, and license key mismatch.
If you are having problems with Windows 0xc004f063 activation error, please follow the instructions below to resolve the problem.
Why does 0xc004f063 Windows activation error occur?
The 0xc004f063 system error is very annoying. It can occur in an operating system that has been activated with a legitimate and approved license key. There are several reasons for this problem:
Third-party software conflicts: Although rare, some third-party programs such as Alcohol 120% and Daemon Tools can conflict with the operating system and compromise the license key.
Window problems: Installed Windows updates may contain activation errors that prevent the operating system from obtaining a license. This usually results in the error message “The BIOS license required for Windows BIOS – 100xc004f063 is missing”. Licensing restrictions related to Windows errors can be easily fixed by running automatic recovery of Windows activation errors.
Damaged system files: Damaged system files may prevent the operating system from checking for activation. If this is the case, you can fix it with the built-in tools: Windows System File Checker (SFC) and Deployment Image Servicing and Management (DISM).
BIOS mismatch: If you reset an already activated PC and try to activate another version of Windows (such as Home, Pro, or Enterprise) while the old key is still stored in the BIOS, the 0xc004f063 error will be removed. The SLMGR utility can help solve this problem.
Server problem: Your license key may not be recognized by MS servers. Contact Microsoft support for help with this problem.
To fix Windows 10 activation error 0xc004f063
Run the activation troubleshooter (Windows 10 only).
Before proceeding with other repair strategies, see if your version of Windows can solve the problem automatically. Keep in mind that Windows 10 includes several different automatic repair strategies that the system can use when it detects a known scenario.
If the problem is caused by any license restriction, the Windows activation diagnostic tool should be able to fix the problem automatically. This integrated tool includes a selection of repair strategies that will automatically fix the problem if your activation problem is already covered by a repair strategy.
IMPORTANT: This method is applicable only if the problem occurs in Windows 10. If the 0xc004f063 error occurs on an older version of Windows, go to the following method described below.
Several affected users confirmed that they were able to fix the 0xc004f063 activation error by running the activation program and restarting the computer. The next time they tried to activate the license key, the process was successful.
Here’s a quick guide to using Activation Error Recovery:
- Press Windows + R to open the Run dialog box. Then type “ms-settings: activation” and press Enter to open the Activation tab in the Settings screen.
- While on the Activation tab, look to the right-hand pane and locate the Activation section (at the bottom of the screen). From there, click on the Troubleshooting button.
- Wait for the utility to start, and then patiently wait for it to scan your system for inconsistencies. If it finds problems that can be corrected, you will be presented with a repair strategy. To make it work, click Apply this fix and wait for the process to complete.
- After applying the fix, restart your computer and wait for the next startup sequence. After the next startup sequence, proceed to the next method described below.
Activate Windows with SLMGR
If you see error 0xc004f063 when you try to activate your PRO key (right after you have sent it) then the problem is probably because your BIOS is still using the Windows security key. This is quite common when a user has previously brought a pre-activated computer and then reset it.
If this scenario applies, your operating system will try to activate the operating system using the key stored in the BIOS, regardless of which activation key you are trying to activate. If you find yourself in this situation, you can override the wrong activation key with a series of commands that you enter on the extended command line. Here’s how to do it:
- Press Windows + R to open the “Run” dialog box. While in the Run window, type “cmd” in the text box and press Ctrl + Shift + Enter to open the Run dialog box. When prompted for UAC (User Account Control), click Yes to grant administrator privileges.
- If you are on the extended command line, type the following commands (press Enter after each command) to change the license key you are using to the correct one
- slmgr / ipk <windows-key>
slmgr / ato
- Note: Keep in mind that *windows-key* is reserved space only. To complete this process, you must replace it with your license key.
- When the process completes successfully, restart your computer and see if the change becomes active the next time you start your computer.
If your version of Windows is still not activated despite a valid license key, go to the next method described below.
Performing SFC and DISM scans
It turns out that one of the most common reasons that can lead to Windows activation error 0xc004f063 is a kind of corruption of system files. In most cases, this problem occurs because a critical activation process is actually affected, so your operating system cannot validate the process.
If this scenario applies to you, the most effective way to solve the problem is to run a set of built-in utilities that can fix local errors and corrupt operating system files. Note that DISM (Deployment Image Servicing and Management) and SFC (System File Checker) can do this, but they do it in different ways.
DISM relies heavily on WU (Windows Update) to replace corrupt items with clean copies, while SFC relies on a local archive to handle corrupt system files. SFC is better at fixing logical errors, while DISM is better at finding corrupted subprocesses.
To maximize your chances of solving this problem, we recommend that you use both utilities to maximize your chances of fixing any corrupted instances that may be the source of error 0xc004f063. Here are some step-by-step instructions on what to do:
- Press the Windows + R keys to open the “Run” dialog box. Then type “cmd” in the text box and press Ctrl + Shift + Enter to open the command prompt with administrator privileges.
- Note: When you see the UAC (User Account Control) prompt, click “Yes” to grant administrator access.
- In the expanded CMD window, enter the following command in sequence and press Enter to execute the DISM command:
- Dism.exe /online /cleanup-image /scanhealth
Dism.exe /online /cleanup-image /scanhealth recovery
- Note: Before starting this procedure, make sure that your internet connection is stable. This is important because DISM uses WU to download clean files that are used to replace damaged items. Just so you know what the commands do: The first (health scan) scans the system for inconsistencies and the second (health recovery) starts the recovery process.
- Wait for the process to finish, then reboot your computer and wait patiently for the next boot process to finish. Then repeat step 1 to open another high PDC prompt. This time, however, enter the following command and press Enter to start the SFC scan:
- sfc / scans.
- Note: Under no circumstances should this process be interrupted before it is complete (even if it freezes for a few minutes). If you do, it will compromise your system and more logical errors may occur.
- After completing the second system file scan, restart your computer and see if the problem is resolved the next time you start your system.
If you have followed the above instructions and error 0xc004f063 still occurs, go to the next method.
Contacting Microsoft Support
If you were unable to activate your version of Windows using one of the above methods and the 0xc004f063 error still occurred, it is best to contact Microsoft support and ask them to activate your operating system.
There are several ways to do this, but it’s most convenient to contact a Microsoft agent at the toll-free number specific to the region you’re in.
Keep in mind that depending on your region and the number of support agents active there, you may have to wait a few hours before contacting a live agent.
After a successful conversation with the person, you will be asked a few security questions to confirm that you have the license key you are trying to activate. If all goes well, your Windows build will be activated remotely.
Frequently Asked Questions
- Click on Start and type "cmd" (without the quotes) in the start search box.
- Right-click on cmd in the list of programs and select "Run as administrator".
- In the command shell, type the following command and press Enter after each command.
- Activate your copy again and see if it works.
Select Start -> Settings -> Update and Security -> Activation, then select Troubleshooting to begin troubleshooting activation issues. For more information about troubleshooting, see Using the Activation Troubleshooter.
To go to this exception path, select Start -> Settings -> Update and Security -> Activation and select Troubleshooting. If the troubleshooter doesn't solve the problem, you'll see a link to reactivate it after you change your hardware. Select it to follow this path. For more information, see Activating Windows 10 after a hardware change.
- Activate Windows over the phone.
- Activate Windows using the command line.
- Use the Slui 3 command.
- Change the product key to the multiple activation keys (MAK).
- Run a system file check.
- Advance Solution from Microsoft.