How to Fix Windows 10 Activation Error 0Xc004F074

The Windows 10 Orange Screen of Death, unlike Blue Screen of Errors, is quite an uncommon error where the hardware is the culprit which is mostly caused by some issues with the GPU. If you are currently facing this problem, then you’ve come to the right place as this post will guide you on what you can do to fix it. There have been reports from users that the Orange Screen of Death is caused by various reasons. Some users reported that they encountered Orange Screen of Death when they were watching a YouTube video, while some were not able to boot into their Windows 10 PCs and encountered an error instead of that either says, FAULTY_HARDWARE_CORRUPTED_PAGE or WHEA_UNCORRECTABLE_ERROR error. In addition, this error can also occur when your computer wakes up from Sleep or while using BitLocker, or while you use a second monitor. Whatever the case is, you can try updating your drivers or lower the clock speed of the GPU. You could also try to fix the DRIVER_IRQL issue in case it’s the one that triggers the error or performs Automatic Repair or uninstalls any recently installed software.

Option 1 – Update your Graphics card drivers

One of the possible reasons why you’re getting the Orange Screen of Death error is most likely related to the Graphics card drivers in your computer. Thus, the first thing you can do to resolve it is to update these drivers by following these steps:

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 2 – Try to uninstall software you’ve installed recently

If you have installed a software or two recently and then suddenly encounter this Orange Screen of Death, then they are most likely the culprits. The best thing you can do is to first check the System Log in the Event Viewer for any additional information in case it’s not the GPU but some other driver or device that’s causing the error. Once you have identified the culprits, uninstall them and see if the error is fixed.

Option 3 – Try disabling Overclocking

If overclocking is enabled, you might have to disable it as some users reported that the WHEA_UNCORRECTABLE_ERROR 0x00000124 error started to appear right after overclocking. To disable it, follow the steps below.

• Go to the Start Menu and open Settings.
• Next, select Update and Security and go to the Recover tab.
• From there, click on Restart now in Advanced startup. This will restart your computer.
• Once you’re in the Advanced startup, go to Troubleshoot and then select Advanced Options.
• From there, select the UEFU Firmware Settings.
• Now click on Restart. Once your computer has restarted, it will automatically open BIOS.
• From the BIOS, go to the Advanced tab and navigate to Performance and then look for Overclocking.
• Once you’ve found Overclocking, make sure that it is disabled. If it’s not, then disable it and then save the changes made by tapping the F10 key.
• Start your computer normally and check if the WHEA_UNCORRECTABLE_ERROR 0x00000124 error is now fixed.

Option 4 – Use the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. And so if you want to fix the Wdf01000.sys Blue Screen error, you need to use the Driver Verifier Manager:

• Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
• After that, select the option “Create custom settings”.
• Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
• Next, select the option “Select driver names from a list” option.
• Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
• Then click on the Finish button.
• Open Command Prompt as administrator and execute this command – verifier /querysettings
• The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
• Open the Command Prompt as admin again and run this command – verifier /reset
• The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 5 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.

• You can start by creating and booting from a bootable Windows 10 USB Stick.
• After that, click on Repair your computer located on the bottom left corner when you are on the initial Windows Startup screen.
• Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
• Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

If you are not able to access the Windows 10 Advanced troubleshooting options within Windows then you’ve come to the right place as this post will guide you on how you can repair or boot the Windows 10 installation without losing data using the bootable installation USB or DVD media. To repair or boot Windows 10 using the installation media, you have to download the Windows ISO, create a bootable USB or DVD drive, boot from the media and select “Repair your computer” and then select Startup Repair under Advanced troubleshooting. To get started, follow the given steps below carefully. Step 1: Frist, download the Windows ISO. Although this is not necessarily needed, it’s still better if you download the Windows ISO first so make sure that you download the same ISO version as installed on your computer. Step 2: Next, create a bootable USB or DVD drive.

• Insert your USB drive into your PC.
• Tap the Win + R keys to open the Run dialog box and type in “cmd” and tap Enter to open the Command Prompt. Alternatively, you can also search for “cmd” in the Cortana search box to open Command Prompt.
• Once you’ve opened CMD, type in this command to open the DISPART utility – diskpart
• After that, you should see a new black and white window that would say, “DISKPART>”.
• Next, type in “list disk” in the command line and tap Enter to see the list of all the Storage devices as well as your hard disk connected to your PC. Here, you have to identify your disk’s number.
• Type in this command where “X” is the disk number you have identified and then tap Enter – disk X
• Type in this command and hit Enter to clear the table records and all the visible data on the drive – clean
• Now you have to recreate a new primary partition of the drive so you’ll have to type in this command and tap Enter right after – create part pri
• A new primary partition has been created so you have to select it by typing this command and tapping Enter – select part 1
• Now you have to format it to make it visible to normal users by typing – format fs=ntfs quick

Note: If your platform supports the Unified Extensible Firmware Interface or UEFI, replace the “NTFS” with “FAT32” in the command on Step 10.

• After that, type in this command and tap Enter after – active
• Finally, type this command and hit Enter to exit the utility – exit
• After you prepare the image for the operating system, save it to the root of your USB Storage device.

Step 3: After creating a bootable drive, boot from the media and select the “Repair your computer” option. Once you boot from the USB drive, it will start the Windows 10 installation right away. So you must not keep on clicking Next as you will end up installing Windows. You need to look for the “Repair your computer” link on the first installation screen and click on it and then boot your computer into Advanced Recovery. Step 4: Select Startup Repair under the Advanced options screen

• Once you’re at the Advanced Recovery screen, select Advanced Options and select Troubleshoot.
• After that, look for the Startup Repair and click on it and then follow the next on-screen instructions. This solution will help you fix issues that do not allow you to boot into your computer.
• On the next screen, you will see the admin account with its name. Click on it and verify using the account password associated with the email.
• After verification, it will start to diagnose your computer and automatically resolve any detected issues related to boot.
• After the issue is fixed, your computer should reboot normally and you should now be able to use it. Note that your personal files are still intact since the process didn’t delete or wipe them out.

As you know, just like other web browsers, Google Chrome offers Incognito Mode or private browsing which you can use to make sure that your browsing activities are not being tracked by any websites you visit and it also keeps targeted ads at bay. On the other hand, signing in to a website, even when in Incognito Mode is a different thing since that website can track your browsing activities. Thus, Incognito Mode is still useful especially if you want to browse the web safely and without getting tracked except when you log in to some site. However, there have been reports recently that Incognito Mode is missing in Chrome and users are clueless as to how or why it happened. If you are one of them, worry not for this post will walk you through what you can do if there’s no Incognito Mode in Chrome on your Windows 10 computer. This is an unusual and strange issue since the Incognito Mode in Chrome is available by default and you don’t have to do anything to enable it. It is possible that there might be corruption in the Windows Registry which caused the disappearance of Incognito Mode, worry not though for there are some tweaks you can apply to restore the missing Incognito Mode. To apply these tweaks, you need to create first a System Restore point, and then once you’re done, follow the instructions provided below carefully. Step_1: Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and then hit Enter to open the Registry Editor. Step_2: Next, after opening the Registry Editor, navigate to this path – ComputerHKEY_LOCAL_MACHINESOFTWAREPolicies Step_3: From there, look for ChromePolicies and locate the DWORD named “IncognitoModeAvailability” and double click on it. Step_4: Edit the value of the “IncognitoModeAvailability” DWORD by changing its value from 1 to 0 so you can enable Incognito Mode in Chrome. Step_5: Once done, exit the Registry Editor and restart your computer and then check if you can now see Incognito Mode in Chrome. On the other hand, there is also another option that allows you to force open your Chrome browser in Incognito Mode. All you have to do is set the value of the “IncognitoModeAvailability” key to “2” instead of 0. This can be useful especially if you always browse the web in this mode. But you need to remember that you won’t be able to go back to the normal mode once you do this. Here are what the values of the IncognitoModeAvailability DWORD actually mean:

• 0 – Incognito mode is enabled by default
• 1 – Incognito mode is disabled
• 2 – Chrome is forced to always open in Incognito mode

Error Code 10 - What is it?

Error code 10 is a type of Window Device Manager error code. This error code is generated when the Device Manager can’t start the hardware device or is experiencing device driver issues. It is displayed in the following format:

"This device cannot start. (Code 10)"

You can access complete details about error codes related to Device Manager such as code 10 through the Device Status area in the Device Properties.

By accessing Device Status, you can easily view the status of each device and learn about the specific device that could be causing the problem.

Solution

Error Causes

Error code 10 can be triggered due to several reasons. These include:

• Outdated drivers
• Corrupted drivers
• Incompatible drivers
• Device configuration issues
• Hardware compatibility problems

Device driver corruption can cause you great inconvenience and PC performance issues. The computer’s operating system relies heavily on device drivers to communicate with the hardware.

For example, the printer driver facilitates functioning of the printer. Similarly, the graphic card driver ensures proper video output on the monitor screen.

However, your PC hardware, such as printer or keyboard, may stop functioning properly if their device drivers become outdated or corrupt. Therefore to avoid inconvenience and to ensure your PC works properly, it is important to resolve the problem immediately without any delay.

Further Information and Manual Repair

To repair error code 10, you don’t have to be a technical whiz or hire a professional computer programmer. Here are some of the best and easy to perform DIY methods that can help you fix this device error in no time.

Method 1 - Reboot Your PC

Sometimes temporary problems in Device Manager can also generate code 10 error. Therefore it is advisable to restart your PC. Rebooting your system might fix the error. Try it! If it does, great, however, if the error still persists, then try other methods listed below.

Method 2 - Reinstall Drivers

Go through the Device Status in the Device Properties to view the driver causing the problem. If any driver is tagged with a yellow exclamation point, it means that driver is the one causing problems. Once identified, uninstall that driver and then reinstall it. This will hopefully resolve the problem.

Method 3 - Update the Device Driver

Whether the error code 10 is generated due to incompatible, corrupted, or outdated device drivers, simply update the device driver to resolve. To update the driver, go to the Device Manager, then click the driver tab in the device properties dialog box.

After that, click update driver. This will start the hardware update wizard. Then follow the instructions to update the driver on your PC. During this process, you may be prompted to provide the driver path.

If you don’t have it, then you will have to download the latest driver from the hardware vendor’s official website. This can be time-consuming and stressful.

Method 4 - Install DriverFIX

Another alternative is to install DriverFIX.  It is a user-friendly device driver management software with an intuitive interface.

Its intelligent algorithm is designed to detect all the problematic drivers in seconds. It automatically updates and accurately installs appropriate drivers and ensures your PC runs at its optimum level in no time.

Click here to download DriverFIX on your system to resolve error code 10.

There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:

• Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
• 0x80041010 WBEM_E_INVALID_CLASS
• When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
• Trying to use wbemtest , and it hangs
• Schemas/Objects missing
• Strange connection/operation errors (0x8007054e)

To verify if there is corruption, you can try running the following command in an elevated Command Prompt:

winmgmt /verifyrepository

 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

• Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
• After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository

The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.

• Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository

This command will perform a consistency check on the WMI repository.

• If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository

This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:

• AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
• AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:

• First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
• If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
• Next, type and enter this command: Winmgmt /resetrepository
• After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
  • net stop winmgmt /y
  • Winmgmt /resetrepository

This should fix the problem.

In their search for making Windows, a better operating system Microsoft has come up with an insider program that will collect telemetry and send it to Microsoft in order to provide enough information to make a better OS. Being in an insider program is per choice basis and it is not forced to anyone. This guide will cover how to turn off the insider program since its constant updates and telemetry can slow down the internet. So if you decided that you no longer want to be part of this program here is how to turn it off.

• Press ⊞ WINDOWS + R to open the run dialog
• Type in dialog gpedit.msc and press ENTER
• You will find yourself in the Local Group Policy Editor Window. Inside windows find: Computer Configuration > Administrative Templates > Windows Component > Windows Update > Windows Update for Business
• Move to the right pane and double-click on the Manage Preview Builds option
• Inside the Manage Preview Builds window, check the Enabled radio button
• Go to the Options section, and using the drop-down menu, set the preferred release channel
• Select Apply and then OK

If the Task Manager is either blank or is not showing processes on your Windows 10 computer, then here are a few things you can do to resolve this issue. This kind of problem can occur due to some system file corruption or some malware infection in the system. Here are some suggestions you can try to resolve the problem with the Task Manager on your Windows 10 PC.

Option 1 – Try restarting your computer

The most common and most of the time effective way to resolve this kind of issue is to simply restart your computer. Thus, you have to restart your computer and see if it helps in fixing the Task Manager issue or not. If not, you can try the next given options below.

Option 2 – Run the DISM tool

If the first option didn’t work, then running the Deployment Imaging and Servicing Management tool can help you resolve the issue with the Task Manager as it will repair the Windows System Image as well as the Windows Component Store in Windows 10.

• After you access the Advanced Startup options, select Command Prompt by using the arrow keys on your keyboard.
• Next, type in this command: DISM /Online /Cleanup-Image /RestoreHealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 3 – Make sure that the display columns are selected in the Task Manager

You have to make sure that you have checked or selected the display columns you want to be displayed. So if none of them are selected, you might not see any details at all. Thus, you need to right-click on the space near Name and select the columns.

Option 4 – Run the System File Checker Scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be the reason why the Task Manager is blank or is not showing processes. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Restart your computer.

Option 5 – Troubleshot the problem in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing the Task Manager issue. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 6 – Try scanning your computer using Windows Defender

As mentioned, the Task Manager issue might be caused by some malware in the system and so to eliminate the malware, you have to scan your computer using security programs like Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

During Windows 10 installation, you will see all the beautiful user interfaces, however, what’s more, important are the drivers, your processor, and free storage disk in order for the installation to be successfully completed. So if you are getting the CompareExchange128 error during the installation of Windows 10, this means that the CPU lacks a very important instruction known as “CMPXCHG16B”. Thus, if you don’t have CMPXCHG16B, then it will result in the CompareExchange128 error when you install Windows 10. In fact, CMPXCHG16B, PrefetchW as well as LAHF/SAHF is a criterion for you to be able to use Windows 10 64-bit version when upgrading from an earlier version of Windows. So what exactly is the CMPXCHG16B instruction? The CMPXCHG16B instruction is the one that performs an atomic compare-and-exchange on 16-byte values. This instruction can also be referred to as “CompareExchange128”. The atomic compare-and-exchange means that the CPU compares the contents of a memory location with a given value. So if the values are the same, it modifies the contents of that memory location to a new given value. Note that this kind of issue only happens to the 64-bit Windows 10 version and the only way to resolve it is by getting an update on the hardware level from the OEM. On the other hand, if nothing really works, it’s maybe time for you to get a new CPU but before you resort to that, in the meantime, you can try following the options given below to fix the CompareExchange128 error during the installation of Windows 10.

Option 1 – Try to update the BIOS and Chipset Drivers

One of the best things you can do to fix the CompareExchange128 error is by updating the BIOS and chipset drivers which is why you need to check if your OEM has an update available for your computer’s BIOS as well as the related chipset drivers. But before that, you need to first check the BIOS version. To do so, follow these steps:

• Type “msinfo32” in the search bar and hit Enter to open the System Information Tools.
• After opening the System Information Tools, check the BIOS version.
• Then take note of that BIOS version. You also need to use the BIOS utility that came with your computer and use it for the upgrade. Note that it is different for every computer and if you don’t have it, you can just go to the OEM website and see if there is an option to download it there.

Option 2 – Try to downgrade to the 32-bit Windows 10 version

If option 1 didn’t work as the BIOS update is not available, you can also try downgrading to the 32-bit version of Windows 10. Keep in mind that this will bring restrictions on the amount of RAM installed and other places but that won’t be a problem as you can still switch.

Option 3 – Try buying a new hardware

If none of the first two options didn’t work for some reason then maybe it’s time for you to purchase new hardware especially if your computer is way too old. In such cases, it’s better to buy new hardware or better yet, a new computer that can keep up for the next couple of years.

Runtime Error 713 is an error that occurs during the distribution of a Visual Basic application that includes a data report. The error is displayed on the screen when you try to open the data report from your desired application.

Error Causes

The reason why computer users often experience the Runtime Error 713 is that the data report run-time file also referred to as Msdbrptr.dll is not included in your setup package. Though this error does not pose any big threat to your computer, however, it is recommended to fix the error because the Runtime error 713 may hamper your ability to install and access new programs.

Further Information and Manual Repair

Don’t you panic if you see Runtime Error 713 message pop up on your PC? This error is rated easy to repair and can be fixed in a couple of minutes. There are two ways to fix Runtime Error 713. You can choose whichever 2 alternatives suit you best.

• Method 1

First, open your project and include a reference to the data report file, the Msdbrptr.dll file. Locating this file is not difficult. It is listed as Microsoft Data Report Designer v6.0 in the reference dialog box. Sometimes you may see this file listed more than once. Now when this happens be sure to select the file that is associated with Msdbrptr.dll. After you select it, the reference will be verified. Once verification is complete, you are good to go. Now you can try rebuilding your setup package again.

• Method 2

The second alternative is to add the Msdbrptr.dll file manually in PDW (the Package and Deployment Wizard). Simply add the file in the Included Files dialog box window and run the PDW. Now you are all set to rebuild your setup package. Whether you follow method 1 or 2 after you rebuild the setup package and the installation is complete, you will see the following files in the indicated folders:

• <windows system>Msdbrptr.dll
• <program files>Common Files\Designers\Msderun.dll
• <windows system>Msstdfmt.dll

The presence of these files indicates successful installation and now you can easily try opening the data report. If you’ve noticed, all you have to do to fix Runtime Error 713 was to include the Msdbrptr.dll file. So, next time if you or your friends experience Runtime Error 713, you know exactly what to do and how to fix it.

Gaming on the computer has become one of the most used past-time activities among people of all ages. And since we are still in pandemic it has only risen as activity. People can acquire a lot of games at various discounts on various platforms and enjoy them at the leisure of their home. Among many game platforms and stores, Electronic art's Origin is one of the bigger ones, and having some titles that could not be found anywhere else coupled with the ability to have access to almost the whole game catalog with one monthly subscription make it one of the most used clients. Sadly as with every piece of software Origin's client is not perfect by any means and it can behave strangely from time to time. Hello everyone and welcome to errortools.com, today we will fix Origin error code 10 which oddly enough can appear out of nowhere and can even appear on the very end of installation for the chosen game. If you have managed to come by this error you are in luck to be here because we have a couple of fixes for it. I know that you might be excited to play the game so let's go and do some fixing

Check Server status

Before diving into technicality and before we start deleting files and fixing things you should check the Server status. This seems maybe like something you should not do but if the server has experienced some kind of downtime or it is in maintenance Origin will throw this error in the client. Unexpected situations can cause various server issues all of a sudden and the first thing is to check are servers online and working. There are various ways to check server status from official origin website to Electronic arts twitter channel to Reddit and many more online server status websites. If it turns out that the server is to be blamed for this error then sit back and wait for EA to resolve the issue, there is not much you can do anyway.

Delete OriginThinSetupInternal.exe

• After some research, it has come to light that originthinsetupinternal.exe can cause this specific error. The best solution is to delete the file and then run Origin as administrator so the file is remade new.
• First, make sure that Origin is fully closed, check the taskbar and if it lurks there right-click on it and click on quit
• Run file explorer and go into the folder where Origin is installed, by default it is C:\Program Files (x86)\Origin
• Locate OriginThinSetupInternal.exe and delete it
• Then locate origin.exe and right-click on it and then click on Run as administrator

Reinstall Origin client

If the previous solution has not solved the issue then Origin might have some corrupted files inside it. It is known that the Origin client can produce some bad files if the installation has been forcefully canceled. The best thing is to reinstall the completely whole client.

• Press ⊞ WINDOWS + R to open the run dialog
• Inside run dialog type in Control panel and press ENTER
• In the control panel locate programs and features group and double click on it
• Locate Origin, click to select it, and on top click on uninstall
• After uninstall process is completed start file explorer and go to the folder where Origin was installed, by default it is C:\Program Files (x86). Locate the Origin folder and delete it.
• Go to the official origin website and download the new client installation.
• After the download is finished double click on it and follow onscreen instructions.

Disable antivirus

If every solution so far has not been able to remove error then obviously something else is interfering with the origin client and installation functioning. Altho not advisable, turn OFF your security suite including both firewall and antivirus and try installing the game again. There is the possibility that the origin client or some game file has been marked as false positive by security software thus preventing it from executing properly.