Fix Windows 10 Error Code 0x800703e3

Windows has a lot of built-in tools that help you fix tons of system-related issues. One of them is the System File Check which is the tool you can use to conveniently replace potentially corrupted or missing system files with good ones. But what happens when it does not work? Well, you’ve come to the right place as in this post, you will be guided on how you can replace a corrupted single Windows system file manually with a known good copy of the file if the System File Checker scan is not working. When you encounter this issue with the System File Checker, it will be unable to replace the corrupted system files and returns an error message instead. And so to fix and replace corrupted system files in your Windows 10 computer without the help of System File Checker, you can refer to the instructions provided below. Step 1: First, you need to open the log files listed below and identify which particular file has been corrupted:

• %userprofile%Desktopsfcdetails.txt
• Log %WinDir%LogsCBSCBS.log

Step 2: You will see all the details on the given log files. Once you find out the name and the path of the file, you have to take ownership of this corrupted system file. Step 3: To take ownership of the corrupted file, you need to pull up Command Prompt by tapping Win + R keys on your keyboard and then type “cmd” and tap Enter. Step 4: After opening Command Prompt, type and enter the command below to execute it:

takeown /f FileNameAndPath

Note: In the given command, “FileNameAndPath” represents the name and the path of the corrupted file. For instance, the corrupted file is named “wuapi.dll”, then you need to type “takeown /f C:/Windows/System32/wuapi.dll” Step 5: Next, you need to grant administrators full access & control to the corrupted file and you can do that via Command Prompt again. Step 6: In the elevated Command Prompt, type and enter the following command to execute it:

icacls FileNameAndPath /GRANT ADMINISTRATORS:F

Note: We’re going to use the wuapi.dll again as an example. So the command should be like this: icacls “C:/Windows/System32/wuapi.dll /grant administrators: F”. Step 7: Now all that’s left to do is replace the corrupted system file with a good copy from a trusted source. Once you have a copy, open an elevated Command Prompt again and execute the following command:

copy NewFileLocation FileNameAndPath

Note: In the command given above, the “NewFileLocation” is the location where you have saved the copy of the file. For instance, if you’ve saved it on your desktop, this is how it should look: “copy C:/Users/<username>/Desktop/wuapi.dll C:/windows/system32/wuapi.dll”

It is a fact that Blue Screen of Death errors can give you a headache for you will have a hard time fixing it as it is one of the most difficult errors you can encounter on your Windows computer. One of these BSOD errors is the UNEXPECTED KERNEL MODE TRAP error. If you receive this kind of error then it means that the operating system was not able to catch a trap or an exception generated by the CPU. This BSOD error has an error code 0x00000007F and indicates that the Intel CPU generated a trap that the kernel failed to catch. One of the most likely causes is hardware failure due to faulty memory. Aside from this cause, you also have to track down other probable causes for this problem like corrupted system files, incompatible drivers or programs, faulty hardware, and even dusty components, and so on. To fix the UNEXPECTED KERNEL MODE TRAP BSOD error, here are some suggestions that might help.

Option 1 – Uninstall the programs you installed recently

Chances are, some programs that you just installed might be the one that’s causing the BSOD error. Thus, you need to uninstall the program to resolve the problem.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it. In addition, you might also want to check the hardware components of your computer that might not support the operating system itself. You can disconnect all the external devices like USB drives, scanners, printers, etc., and then reboot your PC. After that, add the devices again one after the other and check if the BSOD error is now fixed or not. Moreover, you can also perform a clean boot to make things easier for you.

• 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” checkbox 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” checkbox.
• 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.)

Option 2 – Update your device drivers

• Tap the Win + R keys to launch Run.
• Type in devmgmt.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. Look for the device driver you and then select either “Update driver” or “Uninstall device”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• If you have chosen to uninstall the driver, follow the screen options to complete the process and then restart your PC.
• Connect the device and Scan for hardware changes – you can see this option under Device Manager > Action.

Option 3 – Use the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like UNEXPECTED KERNEL MODE TRAP. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 4 – Run the Windows Memory Diagnostic tool

You can use the Memory Diagnostic tool in Windows to check RAM. Before you use this tool, make sure you save all your important work.

• Tap the Win + R keys to open the Run dialog box.
• Next, type in “mdsched.exe” in the field and hit Enter to open Memory Diagnostic.
• After that, the Windows Memory Diagnostic will give out two options such as:

1. Restart now and check for problems (recommended)
2. Check for problems the next time I start my computer

• Select any of the given options. After that, your computer will restart and check for memory-based issues upon the restart. If there are any issues, it will automatically them.

Option 5 – Disable Memory caching in the BIOS

You can also disable memory caching in the BIOS to fix the UNEXPECTED KERNEL MODE TRAP error.

• Open the BIOS Setup screen.
• Next, go to Advanced > Cache Memory and then disable it.
• Tap the F10 key to save the changes made and restart your computer.

Option 6 – Run System File Checker

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow
• Restart your computer once the scan is completed.

Option 7 – Clean your hardware components for dust

Cleaning your computer’s hardware components for dust might also help in resolving the UNEXPECTED KERNEL MODE TRAP error. Make sure to use a soft cloth in cleaning the hardware as well as a small blower. Moreover, ensure that you do not damage any parts with moisture or cause harm to any circuits while you’re at it.

Windows photo viewer was a popular photo viewing application integrated into Windows 7, 8, and 8.1 but in Windows 10 it has been replaced with photos, Microsoft's new application aimed at photo viewing on your desktop. Now if any one of you wonders why should be bringing the old application back to Windows 10 since we have an alternative one, the answer would be resources and speed. The old photo viewer application is lightweight, fast, and reliable, opening the same photo in both photo viewer and in new photos shows us that Microsofts new viewer application takes even three times more RAM, and it's visibly slower in loading times for pictures. Since I am a person who prefers speed and functionality over fancy looks I would be very glad to have the option to bring back a photo viewer. If you have by any chance Windows 10 as an upgrade, bringing back photo viewer is easy as 1,2,3. you just need to open settings and go to default apps, under photo viewer you should see your current default viewing application, probably photos, click on it to see options and choose photo viewer and exit the Settings menu, and you're done. Sadly if Windows 10 has been installed clean on the system and not as upgrade things are a little bit more complicated but do not worry, stay with us, keep reading and you will get there.

Activating photo viewer

How technically photo viewer is still in the system but not used we will have to make it available again and this we will do by adding some lines in the Windows registry, that being said, open a notepad and paste the following code as it is in it.

---

Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\jpegfile\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\pngfile\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open] "MuiVerb"="@photoviewer.dll,-3043" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,36,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-70" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print] "NeverDefault"="" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\DropTarget] "Clsid"="{60fd46de-f830-4894-a628-6fa81bc0190d}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,35,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-72" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,35,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-72" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,37,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-83" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,37,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-71" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\DefaultIcon] @="%SystemRoot%\\System32\\wmphoto.dll,-400" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\SystemFileAssociations\image\shell\Image Preview\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\SystemFileAssociations\image\shell\Image Preview\DropTarget] "{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Photo Viewer\Capabilities] "ApplicationDescription"="@%ProgramFiles%\\Windows Photo Viewer\\photoviewer.dll,-3069" "ApplicationName"="@%ProgramFiles%\\Windows Photo Viewer\\photoviewer.dll,-3009" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Photo Viewer\Capabilities\FileAssociations] ".cr2"="PhotoViewer.FileAssoc.Tiff" ".jpg"="PhotoViewer.FileAssoc.Jpeg" ".wdp"="PhotoViewer.FileAssoc.Wdp" ".jfif"="PhotoViewer.FileAssoc.JFIF" ".dib"="PhotoViewer.FileAssoc.Bitmap" ".png"="PhotoViewer.FileAssoc.Png" ".jxr"="PhotoViewer.FileAssoc.Wdp" ".bmp"="PhotoViewer.FileAssoc.Bitmap" ".jpe"="PhotoViewer.FileAssoc.Jpeg" ".jpeg"="PhotoViewer.FileAssoc.Jpeg" ".gif"="PhotoViewer.FileAssoc.Gif" ".tif"="PhotoViewer.FileAssoc.Tiff" ".tiff"="PhotoViewer.FileAssoc.Tiff"

---

Yup, that is a lot of keys and settings but you are almost done. Once you have pasted text into your new notepad document save it but as .REG, you can name it however you want but it has to be .REG extension. Once the file is saved double click on it to merge it into the Windows registry. You might need to turn off UAC for this operation (check our tutorial on this topic) and accept warning messages but once it is done you should now have an old photo viewer as a choice for your default viewing application. All you have to do now is to go to settings and go to default apps, under photo viewer you should see your current default viewing application, probably photos, click on it to see options and choose photo viewer and exit the Settings menu, and you're done.

Error Code 80070103 –What is it?

Error code 80070103 affects Windows users who attempt to access the latest updates for hardware drivers using Windows Update. Windows 10 users who are affected by this error code will be unable to complete the upgrade process. This error code usually occurs due to the Windows Update attempts to download an incompatible version of a driver or a driver that is already downloaded on one’s device.

Solution

Error Causes

The cause of error code 80070103 in Windows 10 is usually easy to determine. This is due to the fact that the error code only affects users who attempt to access updates related to hardware drivers. In such cases, the error code will only occur if the Windows Update website or tool on your machine attempts to install a driver that is already present on one’s machine or the version of the driver is unsuitable for one’s machine due to lower compatibility.

Further Information and Manual Repair

Manual repair methods are very effective in helping Windows users fix problems related to error code 80070103 as well as other errors. These repair methods can usually be implemented by users with very limited technical skills. In some cases, however, you may need to contact a Windows repair technician, i.e. if you have problems following the manual repair method instructions provided or if the repair methods prove unsuccessful.

In the case of error code 80070103, the problem can be rectified by either hiding the update or reinstalling the hardware driver. Windows users can hide an update on the Windows Update website or via Windows Update within their machine’s Settings. However, users will need to contact their device manufacturer to reinstall hardware drivers in most instances. See below for further details regarding these manual repair methods.

Method One: Hide the Update

In the case where you are informed via an error message box that a driver, for instance, your graphics driver, is incompatible you may need to consider hiding the update to prevent error code 80070103 from reoccurring on your machine.

The incompatible issues will come about when the Windows Update website attempts to download a driver that is already on the device or one with a lower compatibility. When you hide the update, it is in essence, preventing Windows Update from offering this driver in the future. To complete this manual repair method, follow the steps below:

• Step one: Visit the Microsoft Update site 
• Step two: Select Custom on the Welcome page after completing the scan for the updates process
• Step three: Select Hardware, Optional.
• Step four: Open the second update for the graphics card, then select Don't show this update again check box.
• Step five: Review and install updates.

You may also complete this process by opening Windows Update within your computer’s settings, then selecting the Optional update or available link. Once you’ve done this, you may then select the updates you would like to install and hide the update that has resulted in the occurrence of error code 80070103.

Method Two: Reinstall Hardware Driver

In the case where you need to install a hardware driver, you will need to contact the manufacturer of your device. Once you’ve contacted the manufacturer or visit the manufacturer’s official website, you can then install the latest device drivers manually. Read the instructions for the installation of the latest drivers carefully. This will ensure you avoid any problems and improve your chances of successfully fixing error code 80070103.

After you’ve contacted your device manufacturer and completed the process of reinstalling the hardware driver, check Windows Update to see whether or not error code 80070103 has been rectified. If the problem was related to your hardware driver and you successfully reinstalled the driver, the error code will not reoccur when you attempt to download the latest updates for your hardware drivers.

However, you may need to take another approach if this manual repair method fails to fix error code 80070103. For instance, consider getting help from a Windows repair technician who is equipped with the skills and expertise necessary to offer a detailed inspection of your machine. Though the error code is related to one’s drivers, the fact that a Windows error code occurred may mean that your system needs a thorough evaluation as other issues may be present.

Method Three: Download an Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

One of the most useful tools in the Windows 10 operating system is the Windows Media Creation tool. This tool is used to download and install the latest version of Windows 10. However, there are times when you might encounter some issues while using this tool. One of these issues is the Error code 0x80072F76 – 0x20016. If you encounter this error, you will see the following error message during setup:

“We’re not sure what happened, but we’re unable to run this tool on your PC. If you continue experiencing problems, reference the error code when contacting customer support – Error code: 0x80072F76 – 0x20016.”

This kind of error in the Media Creation tool could be due to an interrupted download or unstable internet connection, and many more. To fix it, you can run the Windows Update troubleshooter or try using another browser to download the tool to another location. You can also try changing the DNS or the ISP connection or use the Windows 10 Update Assistant as well as delete the $Windows.~BT & $Windows.~WS folders. Check out the given suggestions below to fix the Media Creation Tool Error code 0x80072F76 – 0x20016 in your Windows 10 computer.

Option 1 – Try to run the Windows Update troubleshooter

Windows 10 have various troubleshooters that can help you resolve many system issues. So if you’re dealing with Windows Update errors like Error Code 0x80072f76 – 0x20016, you can run the Windows Update troubleshooter to resolve it. To run the Windows Update troubleshooter, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 2 – Try using a different browser to download the tool to another location

You could also use another browser in downloading the tool and place it in a different location on your computer but if you do not have another browser, you can just install one and then download the same tool to another location like the Desktop.

Option 3 – Try to change the DNS

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC and then check if the Media Creation tool error is fixed.

Note: If you are using a third-party proxy service, you have to disable it.

Option 4 – Try to change the ISP connection

There are times when the connection to the Microsoft servers is interrupted due to some glitch or it could also be blocked by your Internet Service Provider or ISP. To rule out this possibility, you can try to change your computer’s internet connection and then see if it fixes the problem.

Option 5 – Try to use the Windows 10 Update Assistant

There’s another tool you can use as an alternative to the Media Creation tool. It is called the Windows 10 Update Assistant. This tool can also help you download and install Windows updates seamlessly.

Option 6 – Try to delete the $Windows.~BT and $Windows.~WS folders

From time to time, the Windows Update files also get corrupted which can cause some problems and conflicts when downloading and installing a Windows Update. To fix this, you need to delete the $Windows.~BT & $Windows.~WS folders in your computer.

KMODE_EXCEPTION_NOT_HANDLED – What is it?

Some users installing or upgrading to Windows 10 experienced the theKMODE_EXCEPTION_NOT_HANDLED Blue Screen of Death (or commonly known as BSOD) error. This error can be due to different types of things, ranging from software to driver issues. When you experience this BSOD error while trying to install Windows 10, it will prompt you to restart your computer every single time you experience it. In most cases, you will also not be able to proceed with the Windows 10 set-up.

Solution

Error Causes

The “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:

• Hardware incompatibility
• A faulty device driver or system service

Further Information and Manual Repair

You won’t be able to successfully upgrade or set up Windows 10 if you continue to encounter this BSOD error. Note that this error will always prompt your computer to restart every time it happens, preventing you from completing the Windows 10 set-up.

If you’re not tech-savvy or not capable of debugging this issue, it’s highly advisable to proceed with the basic troubleshooting techniques available in this link.

After troubleshooting, below you’ll find a few solutions to rectify the issue.

Method 1 – Check The Cause of The BSOD Error

Two common causes of the KMODE_EXCEPTION_NOT_HANDLED issue are hardware incompatibility and faulty device driver or system service.

If you experience this error, check first if any of your newly installed hardware is compatible with Windows 10. You can find the required hardware for Windows 10 from this link. 

If all your hardware is compatible with Windows 10, you might need to check the device driver or system service. Review the bug check message. If any of the drivers you have is listed in the message, either disable or uninstall them before upgrading or setting up Windows 10.

You might also find it useful to check the System Log available in the Event Viewer for other error messages that can help you figure out the driver or device that’s causing the error. Running hardware diagnostics can also be useful.

Method 2 – Disable (or preferably uninstall) Software Before Upgrading

If you’re upgrading Windows 10 from Windows 7 or Windows 8.1, you might need to disable or uninstall the software first. First, try uninstalling your Antivirus utility before starting the upgrade. Restart a few times before starting the Windows 10 installation. If you’re upgrading using the Windows 10 update, make sure that you disconnect from your Wi-Fi or Internet LAN (Ethernet) connection as soon as the download reaches 100% before attempting to start the set-up. Other users also reported that the cause of the KMODE_EXCEPTION_NOT_HANDLED issue is BitDefender. If this is what happened in your case, it will show in the error message such as KMODE_EXCEPTION_NOT_HANDLED (bdselfpr.sys). Users reported that a common solution for this is renaming the file. In the case of BitDefender, try renaming it to bdselfpr.s__. However, make sure to do this cautiously. Sometimes, renaming a file will even do more damage than good.

Method 3 – Disable/Disconnect From Hardware

If you’re connected to any general USB devices (such a smart card reader), disable it. If your computer is connected to other external devices, disconnect all of them. Examples of this include gaming controllers, printers, external hard disk, USB keys, and other non-essential devices).

Method 4 – Other Troubleshooting Steps

Other troubleshooting steps include:

• Upgrade using an .ISO file, instead of directly upgrading from Windows Update. When you do this, make sure you’re disconnected from the Internet during installation. If the process started and you forgot to disconnected, it’s best to restart the installation.
• If you’re connected to a domain while trying to set up Windows 10, disconnect and use a local account.
• If you’re using a SCSI hard disk, connect a thumb drive with the drivers for your storage device. While Windows 10 is setting up, click on the Custom Advanced Option. Using the thumb drive, use the Load Driver command to load the SCSI drive.
• Another possible cause of this error is due to BIOS incompatibility. BIOS issues can be solved by upgrading your version of your system BIOS. If you don’t know how to do this, refer to your BIOS manufacturer’s website.

Method 5 – Use A Trusted Automated Tool

If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.

Error Code 8024402C – What is it?

When upgrading to Microsoft Windows 10, some users may encounter Error Code 8024402C. This error, while attempting to update, is a result of five possible issues. The error code itself is not a critical concern, yet while the error is occurring, users will not be able to upgrade their Windows software. As with any Microsoft error code, even if it is not critical, it is recommended that the error be addressed sooner rather than later. An insignificant error now could lead to a larger, more catastrophic error later on. Common symptoms include:

• A dialog box appears with the Error Code 8024402C when attempting to upgrade to Microsoft Windows 10.
• Your current version of Windows is unable to recognize the need for an update to Microsoft Windows 10.

Solution

Error Causes

As previously stated, there are five major reasons why error code 8024402C occurs.

• An erroneous character in the proxy override settings
• A wrongly configured firewall is preventing the update from taking place.
• Attempting to access the Windows 10 update through a VPN (Virtual Private Network) connection.
• Workstations that operate behind a corporate ISA server.
• A corporate network system that does not have auto proxy enabled.

The sooner these known causes are addressed, the sooner you will be able to successfully upgrade to Microsoft Windows 10.

Further Information and Manual Repair

Microsoft Support posits four different resolutions to these known error code 8024402C issues. Some of these methods will be more comfortable for at-home users than others. If you are experiencing this issue in a corporate or business setting, it may be better to have your IT tech or department attempt the methods.

Method 1:  When your firewall is causing the issue.

1. Access your firewall software.
2. Specifically, look into the settings associated with your firewall.
3. Make sure that the following three websites are listed as exceptions to your firewall or proxy.

• https://*.windowsupdate.microsoft.com
• http://download.windowsupdate.com
• http://*.windowsupdate.microsoft.com

4. If any of these websites are missing from your firewall list, add them to the list.
5. Restart your Microsoft Windows 10 update.

Method 2: For an erroneous character in the proxy override settings.

1. Open internet explorer, if you use another program to access the internet, you will still need to use internet explorer for this solution.
2. Open your internet explorer tools window.
3. Click on internet options.
4. Choose the connections tab.
5. Select LAN settings.
6. Choose the Advanced option.
7. Delete anything that appears in the exceptions section.
8. Closeout of internet explorer.
9. Click on your start button.
10. Select RUN and type CMD into the field, press ENTER.
11. This will access the command prompt screen. Type “proxycfg -d” and press ENTER.
12. Type the command “net stop wuauserv” and press ENTER.
13. Finally, type “net start wuauserv” and press ENTER.
14. Now you have cleared your proxy cache. Access the Microsoft Windows 10 update again to download.

Method 3: If a VPN connection is causing error code 8024402C.

1. Disconnect from your VPN connection, thus connecting directly to the internet without a proxy or network.
2. Retry the Microsoft Windows 10 update.
3. After the update is successful, reconnect to the VPN network.

Method 4: Use this is an ISA server is in place at your networked business site.

1. Access the ISA firewall client option. From here your goal is to initiate the ISA server automatic detection feature.
2. From the control panel, select the firewall client option.
3. Choose the configure option.
4. Check the box next to “automatically detect firewall server”.
5. Select the “update now” button.
6. Click the OK button.
7. Restart your Microsoft Windows 10 update.

Again, not all of these methods are meant for computer users who do not usually explore and change software settings of this nature. If you do not feel comfortable with any of these methods, you can opt to download and install a powerful automated tool to repair Windows error code 8024402C.

As you know, Bluetooth headphones allow users to connect to their mobile devices wirelessly. This allows you to talk on your mobile device or listen to music without having to connect any cords or wires. Additionally, it even allows you to adjust the volume of a left or right speaker. However, Bluetooth headphones in Windows 10 are another story as their scope is limited. For instance, the left and right pieces can’t have different volume levels. But if you still want to change the dual control of the volume of headphones separately in Windows 10. And in this post, you will be guided on how exactly you can do that. In addition, in this post, you will also be guided on what you can do if the Windows Update messed with the Bluetooth volume control and what you can do to disable the absolute volume in Windows 10. In case you don’t know, the Absolute Volume feature is actually incompatible with a number of Bluetooth devices which can result in the inability of the Bluetooth device to adjust its volume. Thus, if you experience this kind of issue, you’ll notice that the volume slider in the taskbar and the device volume control neither have any effect in adjusting the volume. And each time you try to adjust the volume level for one speaker, the volume of another speaker also automatically changes. In such a case, it would be difficult for you to separately change the dual volume control headphones. Worry not for there is an easy registry tweak you can try to make this possible to do. But before you proceed with the instructions provided below, make sure that you create a System Restore first. Once you have that covered, follow the steps below carefully. Step_1: Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor. Step_2: Next, navigate to this registry path: HKEY_LOCAL_MACHINESYSTEMControlSet001ControlBluetoothAudioAVRCPCT Step_3: After that, look for the entry named “DisableAbsoluteVolume” which should be located in the right pane. But if you’re unable to find this entry, you can just create it by right-clicking on the CT key and selecting New > DWORD (32-bit) value, and then assign “DisableAbsoluteVolume” as its name. Step_4: Once done, double click on the “DisableAbsoluteVolume” DWORD and set its value from 0 to 1. Step_5: Now exit the Registry Editor and restart your computer. On the other hand, you can also disable or enable the Absolute Volume feature by executing a command in the Command Prompt.

• If you want to disable the Absolute Volume feature, just execute this command: reg add HKLMSYSTEMControlSet001ControlBluetoothAudioAVRCPCT /v DisableAbsoluteVolume /t REG_DWORD /d 1 /f
• If you want to enable the Absolute Volume feature, just execute this command: reg add HKLMSYSTEMControlSet001ControlBluetoothAudioAVRCPCT /v DisableAbsoluteVolume /t REG_DWORD /d 0 /f

After you execute the command, just restart your computer.

After your computer restarts.

Once you’re done executing the given instructions above, you have to right-click on the speaker icon located in the system tray and select Open Sound Settings and click on Manage device settings – the same controls will be visible to you like earlier. Now when you change the volume level for one speaker, the other speaker should now remain as it is and won’t change alongside the speaker.

In case you don’t know, Microsoft Office uses a separate mechanism than the Windows operating system for specific purposes such as Updates and Activation which brings in the content dependencies of this mechanism on different services and processes. Thus, in such cases, you could encounter errors like the error code 0x80070426. When you get this error, you will see the following error message on your screen:

“An unexpected error has occurred. Your request cannot be processed at this time. Please try again later. (0x80070426)”

This kind of error is caused by various supporting processes and services that are not working or are not being triggered as they were supposed to. If you are currently facing this issue, worry not for this post will guide you in fixing it. There are two potential fixes you can try – you can either check the responsible services or manually run the Activation Script. For more details refer to the given options below.

Option 1 – Try checking the responsible Services

• In the Start search, type “services.msc” in the field and tap Enter or click OK to open the Windows Services Manager.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed to the Windows Services Manager utility window.
• After that, look for the “Software Licensing Service” service entry from the given list of services inside the window.
• Then right-click on it and select Properties and from there, make sure that its Startup Type is set to Automatic.
• Once done, click on the Start button to start the service and then exit the Services Manager.
• Next, tap the Win + R keys to open the Run utility and then type “cmd” in the field and tap Enter to open an elevated Command Prompt.
• After that, type and enter each command below one after the other.
  • net start slsvc
  • sc qc slsvc
  • sc queryex slsvc
  • sc qprivs slsvc
  • sc qsidtype slsvc
  • sc sdshow slsvc
• Now check if the problem is fixed or not.

Option 2 – Try to manually run the Activation Script

• In the Start search, type “cmd” and right-click on Command Prompt from the given search results and then select the “Run as administrator” option to open Command Prompt with admin privileges.
• Next, navigate to the following location inside the Command Prompt command-line utility if you are using Office 16.
  • x86: C:/Program Files (x86)/Microsoft Office/Office16
  • x64: C:/Program Files/Microsoft Office/Office16

• On the other hand, if you are using an older version, go to the following location instead.
  • x86: C:/Program Files (x86)/Microsoft Office/OfficeXX
  • x64: C:/Program Files/Microsoft Office/OfficeXX
• Once you’re in the location, type the following command to run the Activation Script and then tap Enter.

cscript ospp.vbs/act

• The command you just entered will activate your copy of Microsoft Office.

There are times when system files get corrupted and if the Windows Update process finds the system’s integrity questionable, chances are, the update, upgrade or the installation may fail and you will only be getting an error code 0x80073712 instead of completing the process. The error code 0x80073712 indicates that a file needed by the Windows setup or the Windows Update is most likely missing or damaged. To resolve the problem, here are some suggestions you can try.

Option 1 – Try running the DISM Tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt as admin.
• Then type in this command: exe /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.

After you run this tool, a log file is created at C:WindowsLogsCBSCBS.log. On the other hand, if the Windows Update client is already broken, you will be prompted to use a running Windows installation as the repair source or use a Windows side-by-side folder from a network share, as the source of the files. Although the chances of this happening are less, if it turns out to be the case, you need to run an advanced command in the DISM tool to repair a broken Windows Update. Just repeat the process above but use the following command instead:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Option 2 – Try running the System File Checker

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 causing the error 0x80073712. 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.

Option 3 – Try running the Chkdsk utility

You can also try running the Chkdsk utility to resolve the Windows Update error 0x80073712. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the Chkdsk utility comes in. The Chkdsk utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the commands listed below, and don’t forget to hit Enter right after you type in each one of them and if you have installed Windows to some different directory, you must replace “C” with the name of the drive you’ve installed Windows with.
• chkdsk C: /r /x
• chkdsk C: /f

Note: The Chkdsk function might take a while before it finishes its operations so you need to be patient and wait until the entire process is completed.

Option 4 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update error 0x80073712. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button.

Option 5 – Try running Microsoft’s online troubleshooter

You also have the option to run Microsoft’s online troubleshooter which could help you fix Windows Update errors.