Fix: Media Creation Tool Error 0x80072f76 0x20016 Install Windows 10

Error 0x80072f76 0x20016 commonly occurs at the time a user tries to use Media Creation Tool for the installation of Windows 10. It is reported to happen after a couple of seconds after launching the Microsoft Refresh tool or MCT. The issue can evolve because of an unstable internet connection, an interrupted download or many more. Before that, let’s have an eye on the causes responsible for it in below part –

Ways to fix Media Creation Tool Error 0x80072f76 0x20016 Install Windows 10

Here is how to Media Creation Tool Error 0x80072f76 0x20016 Install Windows 10 –

1] Run Windows Update troubleshooter

Sometimes, Error 0x80072f76 0x20016 error takes place due to Windows Update related issues. In this respect, you can seek favor from Update Troubleshooter. This is a handy a Microsoft tool equipped with various repair strategies and can resolve the issue effectively. Here is the way to move on –

2] Fix Corruption in Windows Update files

The issue is very likely to occur when System Files have corruption inside especially in the Windows update components. If that happens, renaming the SoftwareDistribution and Catroot2 folder may be a perfect solution. Additionally, clearing WINDOWS.

WS cache folders will be helpful.

Windows Update components often gets corrupted and end up throwing Media Creation Tool Error 0x80072f76 0x20016. In that scenario, resetting the Windows Update components might easily resolve the issue. To accomplish the workaround, guidelines are as follows –

Ren %systemroot%\SoftwareDistribution SoftwareDistribution. bak

Ren %systemroot%\system32\catroot2 catroot2.bak

Important – Above commands will force the Operating System to create new folders for software distribution, which will help to avoid any issues caused by file corruption.

net start wuauserv

net start appidsvc

net start cryptsvc

WS folders. To access the workaround, proceed with below instructions –

4] Modify the AllowOSUpgrade value using Registry Editor

You might be confronting Media Creation Tool Error 0x80072f76 0x20016 because your current Windows version is configured to reject an OS upgrade. If that happens, you need to edit the value of AllowOSUpgrade going through Registry Editor. The detailed process is as follows –

5] Perform a Refresh using Windows Security

One of the best ideas to resolve Error 0x80072f76 0x20016 is to perform Refresh using Windows Security. You can proceed to the resolution using the below guidelines –

6] Disable S. M.A. R.T from BIOS settings

0x80072f76 0x20016 error code might be a cause of S. M.A. R.T. feature in BIOS settings. Often HDD/SSD monitoring system can trigger this issue in devices with a specific configuration. Hence, disabling S. M.A. R.T feature from BIOS will be useful. Here is how to disable the feature –

Hopefully, 0x80072f76 0x20016 error will not appear again in your Device.

7] Use another browser to download MCT

There might be issues with default browser while downloading Media Creation Tool from its site. In that case, try changing the Browser in use. If you don’t have any more browsers, install a new one. After that, Download and Install the Media Creation Tool from another authorized location unlike the earlier one.

8] Try to Change the DNS to another

Switching DNS server might help in resolving Media Creation Tool Error 0x80072f76 0x20016. Here is how you can accomplish the task –

Important – in case of using a third-party proxy service, you have to disable it

9] Change the ISP connection

Media Creation Tool Error 0x80072f76 0x20016 may occur when Microsoft server gets interrupted due to some bug. If it is blocked from Internet Service Provider or ISP, the same result will be there. To fix the issue, you can change the Internet connectivity and check of it resolved the error.

10] Try using Windows 10 Update Assistant Either

Rather than Windows Media Creation Tool, we have another handy utility to upgrade or install the current version of OS. Windows 10 Update Assistant is also competent to seamlessly help you to perform the Windows Updates.

That’s all about the resolutions in order to Media Creation Tool Error 0x80072f76 0x20016 Install Windows 10. Hope you have already resolved the issue.

Fix: Error Code 0x80072f76 – 0x20016

Some users are seeing the 0x80072f76 – 0x20016 error code when trying to use the Media Creation Tool or when trying to install Windows 10 or Windows 8 via Windows Installer. The error is typically reported to occur a few seconds after the Media Creation Tool or Microsoft Refresh Tool is launched.

“Something happened 0x80070002 – 0x20016” Error

What is causing the 0x80072f76 – 0x20016 Error Code in Media Creation Tool?

We investigated this particular issue by looking at various user reports and the repair strategies that most affected users have successfully used to get to the bottom of the issue. Based on our investigations, there are several repair strategies that are known to trigger this particular error:

If you’re struggling to find fixes that will resolve this particular error message, this article will provide you with several troubleshooting guides. Down below, you’ll discover a collection of methods that other users in a similar situation have successfully used to resolve the 0x80072f76 – 0x20016.

The potential fixes below are ordered by efficiency and severity, so please follow them in the order that they are presented. One of them is bound to resolve the issue in your particular scenario.

Method 1: Running the Windows Update troubleshooter

Some affected users have reported that the issue was resolved after they ran the Windows Update Troubleshooter – a Microsoft tool that is equipped with various repair strategies that might end up resolving the issue automatically.

Here’s a quick guide on how to run the Windows Update troubleshooter:

If you’re still encountering the same error message, move down to the next method below.

Method 2: Setting the Compatibility Mode to Windows 8

Some users have been able to resolve the 0x80070002 – 0x2001 error after discovering that the Media Creation Tool was opening in Compatibility mode set to Windows XP. Most users have reported that changing the Compatibility Mode to Windows 8 and making sure that the Media Creation Tool is opening with administrative privileges ended up resolving the issue for them.

Here’s a quick guide on ensuring that Compatibility Mode is set to Windows 8 for the Media Creation Tool (with admin access):

If you’re still encountering the 0x80072f76 – 0x20016 error, move down to the next method below.

Method 3: Resolving corruption related to Windows Update

As it turns out, this particular issue can also occur if the culprit that ends up causing the 0x80070002 – 0x2001 is corruption with the Windows Update component files. If this scenario is applicable to your current situation, then resetting the Windows Update component should resolve the issue and allow you to use Media Creation Tool without encountering the 0x80070002 – 0x2001 error.

Here’s a quick guide on how to do this:

If you’re still seeing the same error message, move down to the next method below.

Some users have reported that the 0x80070002 – 0x20016 error was finally resolved after they erased the contents of the $WINDOWS.

BT and $Windows.

WS cache folders. These contain files needed to create the installation media, so clearing their contents might resolve corruption-related issues.

Note: Chances are the two folders are not visible when you access your Windows drive. In this case, using the ribbon bar at the top, go to View and make sure that the box associated with Hidden items is checked.

Click View Then Check Unhide Hidden Items To Make Sure All The Folders Are Shown

Once the two folders are visible, open each folder individually and empty its contents by selecting every item and choosing Delete.

Once the two cached folders have been cleared, restart your computer and see if you’re still encountering the 0x80070002 – 0x20016.

If you’re still seeing the same error message, move down to the next method below.

Method 5: Editing the AllowOSUpgrade value via Registry Editor

You might be seeing this particular error message because your current Windows version is configured to reject an OS upgrade. If this scenario is applicable, you’ll see the Something happened 0x80070002 – 0x20016” error when trying to run the Media Creation tool to upgrade an existing installation.

This is typically reported to occur with Windows 7 or Windows 10 computers that are eligible to upgrade to Windows 10 but haven’t received the notification to reserve a copy because of a Registry value.

Here’a step-by-step guide that will help you change the AllowOSUpgrade value. This will allow you to use the Media Creation tool without receiving the 0x80070002 – 0x20016 error. Here’s what you need to do:

If you’re still encountering the same error message, move down to the next method below.

Method 6: Performing a Refresh via Windows Defender Security Center

If you went through all these methods without success and you’re trying to use the Refresh tool from Microsoft, you can complete the procedure from Windows Defender Security Center.

This procedure will allow you to Refresh your PC in those instances where the official Microsoft Refresh tool produces the 0x80070002 – 0x20016 error. This procedure is typically known to be effective on Windows 10 builds that already have the Creators Update.

Here’s what you need to do to perform a Refresh via the Windows Defender Security Center:

Method 7: Disabling S. M.A. R.T

Some affected users have reported that they managed to resolve the issue by disabling the S. M.A. R.T. feature from their BIOS settings. As it turns out, this HDD/SSD monitoring system can end up triggering 0x80070002 – 0x20016 error on certain PC configurations.

If this scenario is applicable, disabling the S. M.A. R.T. feature might allow you to perform the operation without encountering the error message again. Here’s a quick guide on disabling the S. M.A. R.T. feature:

Once the next boot sequence is complete, recreate the same action that was previously triggering the 0x80070002 – 0x20016 error and see if the issue was resolved.