Fix Error 0x80244018 when Installing Apps

If you find that your headphones are suddenly not working, read on as this post will help you sort out the problem. There could be several reasons why your headphone is malfunctioning, it could be due to an update you just installed, or it could also be due to incompatible operating system, drivers, and so on. Although updates are created to fix bugs on a computer, there are times when it also causes some issues in the computer. One of the issues it causes is the broken headphone. When this happens, the computer will stop playing any audio using the headphones. The problem, as pointed out, could be due to Windows Updates or incompatible or corrupted drivers in the system. To resolve this problem with the headphones, there are several fixes you can check out. Make sure that you follow each one of the given potential fixes below.

Option 1 – Try to set the headphone as the default device manually

There are times when you plug a headphone, it does not toggle the default audio device. Thus, to fix this issue, you have to set the default audio device to the headphones manually. To do that, follow these steps:

• First, right-click on the volume icon located on the system tray.
• Next, select the Open sound settings option to open the Sound section in the Windows 10 Settings app.
• After that, go to the Output section and select Headphones for the “Choose your output device” option. This should fix the problem for you.

Option 2 – Try to update, rollback or reinstall the Audio driver

If the glitch in your audio has something to do with software, chances are it might be related to the audio driver – it could be that the newest version of your Windows 10 does not work well with the old version of the driver. This is why you have to update your audio driver to the newest available version.

• Tap the Win + R keys to open the Run dialog box and then type in MSC and tap Enter or click OK to open the Device Manager.
• Expand the section for the outdated device drivers.
• And then select the outdated driver(s) and right-click on it/them.
• From the drop-down menu, select the Update Driver option and follow the on-screen instructions to install the latest version of the driver.
• Then also click on the option, “Search automatically for updated driver software.
• Restart your PC after the installation.

Note: If updating the Audio driver didn’t work, you can go to the website of your PC manufacturer and look for the support section where you can download the drivers for your computer. You just need to take note of your PC’s correct model and model number so you can find the appropriate driver.

Option 3 – Try checking the status of the audio-related Windows Services

The Windows Services manages audio for all Windows-based programs and if this service is stopped, audio devices, as well as effects, will also be affected and if this service is disabled, any services that depend on it explicitly will fail to start. So you need to check the status of this service. How? Follow the steps below.

• Tap the Win + R to open the Run dialog box.
• Then type in “MSC” in the field and tap enter to open the Windows Service Manager.
• Next, navigate down to the Windows Audio Service and double-click on it to open Properties.
• After that, set the Startup Type to Automatic and then click on the Start button and if it has already started, stop it and then start it again.

Note: You should also make sure that the following Dependency Services are started and have Automatic Startup type:

1. Remote Procedure Call
2. Windows Audio Endpoint Builder

You should also start the Multimedia Class Scheduler and set it on Automatic if you have it in your system. The Multimedia Class Scheduler Service or MMCSS is a service in Windows that allows multimedia applications to get prioritized access to CPU for time-sensitive processing like the multimedia applications as well as prioritized disc access to make sure that the process does not lack data to process.

Option 4 – Try running the Playing Audio Troubleshooter

Since the Windows 10 operating system has the Playing Audio Troubleshooter, you can use this troubleshooter to try and fix the problem with the headphones. You can access this tool in the Control Panel or in the Taskbar Search and even on the Troubleshooters page of Windows 10. Run this troubleshooter and see if it can fix the issue or not.

Option 5– Try to rollback or install a newer Windows Update

As mentioned earlier, the issue with the headphones could be due to a Windows Update. Thus, to fix the problem, you can try to either roll back or install a newer Windows Update.

Sometimes, some applications after they are installed will put their shortcut in the context menu (right-click on desktop) for easy access, most of the time these are some system tied applications like AMD and Nvidia control panels or archives like WinRAR or 7ZIP but it can happen even for some usual application to do this.

There are some applications that you use frequently and they could be worth putting in the context menu, if you want to avoid clutter on the desktop or in the taskbar this is the third place that you should consider placing shortcuts.

Doing this will require some playing and tweaking in the Windows registry editor so be careful when editing the registry since bad entries can lead to system crash or instability. Follow step-by-step instructions.

Adding apps to the context menu in the registry

Creating entry

Open the registry editor by searching Regedit and pressing enter than inside of the registry editor search for the next key:

HKEY_CLASSES_ROOT\Directory\Background\shell

Select shell and right-click on it, hover over New and in the submenu click on Key. In the next step, you need to name a key, this name will be the thing that will be shown in the context menu when you right-click on a desktop so type in the name that you would like or the name of the application that you wish to add to the menu.

If you wish you can even add a keyboard shortcut to launch this specific application. To do this select entry that you have created and edit the default value, inside the edit string in the Value data field type first & and after that key that you would like as a shortcut. Now after right click if you hit your shortcut key app will be launched right away.

Adding command

The next task is to create a command key that will actually hold the command to launch the application. Right-click on the entry that you have created, hover over New, and click on Key.

Next, you’ll need to create the command key that will actually hold the command used to launch the application. Right-click on the new Notepad key, and then choose New \ Key from the menu. Name this key 'command', all in lower case and without hyphens.

Now in order to finish setting the launcher, you need the full path of the file that you would like to run. Locate your file in file explorer or in another tool and copy its path by SHIFT + right-clicking on the file itself and choosing copy as path option.

Now click on the command key and double click on the default key on right to edit it, inside the field value data paste your path to executable. close and save the registry and you are done.

Windows 10 and Windows 11 have automatic dynamic screen brightness depending on the surrounding light inside the room. Please take note that this option is available only on devices with build-in screens like laptops, tablets, and all in one desktop PC. If you are connected with your PC via an external monitor you will not have these settings available and probably feature is not even working.

Some computers will also allow automatic brightness changes also on what is displayed on the screen. This option is meant to save battery life on devices. Microsoft calls this automatic brightness feature Content adaptive brightness control. In order to change this setting, we will go to settings inside Windows.

Disabling automatic brightness inside Windows

Open Settings inside Windows, in Windows 11 press WINDOWS + I to open settings, then click on the system in the sidebar and then go to Display. Click on the small arrow beside the Brightness slider in order to expand a small menu and then uncheck Help improve battery by optimizing the content show and brightness. If you see Change brightness automatically when lighting changes, uncheck that as well. Close the settings and you are good to go, now brightness will always be as set in settings.

Inside Windows 10, go to Settings and then go to System and then in Display under the Brightness and Color section look below and locate the box that says Automatically adjust contrast based on the displayed content to help improve battery and uncheck it, if the box below with text Change brightness automatically when lighting changes exists, uncheck it as well. Close settings and you are done.

Error 0xA00F4244 or 0x200F4244 is when Windows can not detect the WEB camera in your system and it is usually accompanied by the message: We can’t find or start your camera. There could be several reasons for this error and in this guide, we will cover all of them in order to help you to get back on track and start using your WEB camera which is perhaps now more required than ever in this world we live in.

1. Check privacy settings

   With the latest Microsoft Windows updates come the latest issues and it is not strange that privacy settings can become reset or changed when an update is applied. This is a quick fix to this issue and can be the sole reason why you get this error, go to Windows settings, then to privacy and check to see if the WEB camera is turned OFF, if this is the case turn it back ON and make sure that option Allow apps to access your camera is also set to ON.

2. Check if the camera is enabled

   Sometimes it is by mistake, sometimes by an update but the web camera could be disabled in the device manager of Windows. Right-click on the Windows Start button and click on device manager to open it up, find and expand the cameras category. Right-click on your camera, if it is disabled, you will have the option to enable the camera, if it is enabled and Windows is detecting that it is working fine you will have the option to disable it.

3. Check antivirus settings

   Antivirus and firewall applications are in today's world and life-essential piece of software but they can sometimes create more harm than good, from stopping windows updates to killing important services of applications and preventing internet access being just some examples of their paranoid behavior. Try disabling or turning your protection software OFF and see if your WEB camera will miraculously come back to life. If this is the case, somewhere in the settings of software there is an option that controls this aspect, try to locate it and set it in that way so you are able to use your camera.

4. Reinstall camera driver

   If the previous three solutions failed to produce a satisfactory solution then reinstalling the camera driver might fix the problem. Go to your manufacturer's camera website and download the latest driver for your camera. Go to the device manager and uninstall the driver for the camera, then apply the latest driver and reboot the system.

5. Check connections and cable

   Sometimes an issue is not due to software nature, sometimes it is hardware. Try checking connections and plug the camera in another USB port, twist and turn the cable a little to see is issue cable-related.

6. Check to see if the application supports your camera

   If Windows has detected the camera and is not reporting any issues with it check your application to see if it can detect your camera and that it supports it fully. Sometimes newer applications tend to support only newer camera models. Try to use the camera in other software as well to see if the problem is with the application you are using.

7. Try camera on another computer

   If everything else fails, try the camera on another computer to see if it will work there. If the camera is not working there as well it is probably malfunctioned and broken for good. If it does work there, try to find out what is different in that computer in comparison to yours, maybe it is some service running in the background, certain application configuration, Windows version itself, USB port version, or something else.

In an operating system, it is ideal for an administrator to have permission to access all the folders and files. However, there are times when you try to access the security settings or attempt to view the properties of a file, you could encounter an error saying, “You do not have permission to view this object’s security properties, even as an administrative user”. This kind of error may be caused by several reasons. For one, if your computer is infected with a virus or malware which might have caused some changes to the concerned folder or file. It could also occur if a program or service is using the folder or file simultaneously which explains why you’re not able to access the system. It could also be that the folder or file might have been owned by a user account that no longer exists or you might not have the permissions to view the targeted folder or file even though you’re logged in as administrator. To fix the “You do not have permission to view this object’s security properties, even as an administrative user” error, here are some options that might help.

Option 1 – Put your computer in a Clean Boot State

You can also troubleshoot the problem in a Clean Boot state. It could be that there are some third-party applications in your computer that’re preventing you from accessing security settings or properties of a file and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• 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.)
• After you’ve set your computer into a Clean Boot State, try to check if the error is now fixed and that you can now view the Properties.

Option 2 – Try booting your computer into Safe Mode and delete inactive users

Aside from the Clean Boot State, you can also reboot your computer in Safe Mode and then delete all the inactive users. There are instances when the folder was created or owned by a user account that’s either deleted or inactive now and so you need to get rid of these inactive user accounts to resolve the error.

• First, boot your computer in Safe Mode.
• Then right-click on the concerned folder or file and select Properties.
• Next, select Advanced in the Security tab and click on Add.
• A new window will appear and from there, click on “Select a principal”.
• And then type the name of the user to who you wish to give permissions in the “Enter the object name to select” box.
• Now select Check Names and this would resolve the user name.
• After that, click OK to save the settings. This will close the window and take you back to the previous one.
• Next, from the drop-down menu, change the Type to Allow and select the Full Control checkbox.
• Click OK to save the changes made and then restart your computer in a normal mode.

Option 3 – Try to take ownership of the folder or file

Another thing you can do to fix the problem is to take ownership and force the system into giving permissions to the Administrator. How? Refer to these steps:

• Type “command prompt” in the Windows Search bar and then right-click on the relevant search result and select “Run as administrator”.
• After that, if a User Account Control or UAC prompt appears, just click on Yes to proceed.
• Next, type and enter this command: TAKEOWN /F <path>
• Note that the <path> is the location of the folder or file in File Explorer.
• Now type and enter this second command: ICACLS <path> /grant administrators:F
• Finally, once the command has been executed, restart your computer and then see if you can now access the folder or file.

Option 4 – Try scanning your computer using Windows Defender

As mentioned, the error when accessing the security settings or properties of a folder or file might be due to a virus or malware. It could be that it had made some modifications that prevents you from accessing security settings or properties. To eliminate it, 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.

If you have encountered the “Windows Cannot Find a System Image on This Computer” error while you are trying to restore a system image, then read on as this post will guide you in resolving this problem. A system image is basically a backup of your whole data in the system. For instance, it can be the backup data of your hard disk or the whole hard disk itself, or one of the volumes. This is really useful in some cases like when you are not able to get back into your system for some reason or when your system has been corrupted. In such cases, you can utilize this feature and get going safe and sound. However, not all things go the way as expected like when you make a system image of a drive for instance, or use that backup to restore data and you suddenly encounter the “Windows Cannot Find a System Image on This Computer” error. This kind of error occurs due to a number of reasons but worry not for your data is safe and you can fix this error easily. This error is most likely triggered by changing the name of the “WindowsImageBackup” folder. Renaming this folder will certainly be an issue since it is the one that stores all your data. Aside from renaming the WindowsImageBackup folder, renaming the sub-folders can also cause this error which means that renaming the sub-folders of the WindowsImageBackup folder can trigger the error. To fix this error, here are some suggestions that might help:

Option 1 – Try putting the WindowsImageBackup folder in the Root directory

Windows will have issues finding the WindowsImageBackup folder if it isn’t in the root directory of the drive so if it is not there, the “Windows Cannot Find a System Image on This Computer” error will pop up. When a folder is in a root directory, it means that it shouldn’t be stored within a folder but in the main directory instead.  Thus, you need to put the WindowsImageBackup folder in the root directory to fix the error.

Option 2 – Don’t add any sub-folders in the WindowsImageBackup folder

Another cause of the error is when you add sub-folders in the WindowsImage Backup folder. Adding any sub-folders in this folder will only trigger the error so you should leave the folder as it is and you must not make any modifications to it. So if you have added sub-folders in it, make sure to remove them right away.

Option 3 – Make sure that there is one system image per USB drive

The error can also appear if you’ve stored multiple images inside a single USB drive as it could confuse Windows and will trigger the “Windows Cannot Find a System Image on This Computer” error. Note that storing system images of different volumes of your hard disk in a single USB will prevent you from restoring your data.

Option 4 – Try renaming the System Image folder

If you’ve just changed the name of the System Image folder after you store it on a USB stick or other external device, then it’s no wonder why you’re getting the “Windows Cannot Find a System Image on This Computer” error. Windows search for the default name, “WindowsImage Backup” folder when restoring your data so if it is not able to find it, it throws up this error instead. To fix the error, you need to change the folder back to its default name which is “WindowsImageBackup”.

Option 5 – Check the WindowsImageBackup sub-folders

As mentioned earlier, renaming sub-folders in the WindowsImageBackup folder can trigger the error so if you have renamed sub-folders in this folder, you need to change them back to their default names so that you can restore your data peacefully.

One of the cool and interesting features in Windows is the Screensaver which allows users to display animation or change the wallpaper automatically when the computer is not being used. This feature can also time out and lock your computer when it remains idle for quite some time. However, if you notice that the screensaver of your computer turns on a lot earlier, then you’ve come to the right place as this post will guide you on how you can change the timeout settings of the screensaver of your Windows 10 computer. Usually, the screensaver in Windows 10 is turned off by default, however, if some other user has turned it on or if you have turned it on, you can actually change the timeout settings of the screensaver using several methods. You can do it through the Personalization settings, Registry Editor, as well as the Group Policy Editor. Before you proceed with the instructions provided below, make sure that you create a System Restore point first. Once done, follow each one of the suggestions carefully to successfully change the Screensaver timeout settings in Windows 10.

Option 1 – Modify the timeout settings of Screensaver via Personalization settings

• Open the Start menu and type “screen saver” in the field.
• On the search results that appear, click on the “Change Screen Saver” option.
• From there, you have the option to change the screen saver type, preview, open settings, change the wait time, as well as choose to display lock screen on your resume.
• Now to change the timeout settings of your screensaver, you have to increase the wait time from 1 to 15 or anything that works for you.
• Once done, click OK and exit to save the changes made.

Option 2 – Try to change the screensaver time via Registry Editor

The next option you can try to change the timeout settings in the screensaver is using the Registry Editor. To get started, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry path: ComputerHKEY_CURRENT_USERSoftwarePoliciesMicrosoftWindows
• From there, right-click on Windows located in the right pane and select New > Key.
• Name the key as “Control Panel” and right-click on it and select New > Key and then name it as “Desktop”.
• Once done, click on the newly created Desktop key to highlight it.
• After that, right-click on any empty space in the right pane and select New > String Value and then type “ScreenSaveTimeOut” and hit Enter to save it.
• Now right-click on ScreenSaveTimeOut and select Modify and then set its value data in seconds.
• Click on OK and exit the Registry Editor to save the changes made.

Option 3 – Change Screensaver timeout settings via Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to User Configuration > Administrative Templates > Control Panel > Personalization.
• Then look for a policy setting named “Screen saver timeout” and double click on it and then click on the Enabled option to enable it.
• Add the screen timeout in seconds and click on the Apply and OK buttons to save the changes.
• Restart your computer.

Note: If you want to disable the screensaver feature in your computer, you can always do so by disabling a policy setting named “Enable Screen Saver”.

What Is 0x00000050 Stop Error?

While running your Windows 7/Windows Server 2008 R2, your system suddenly stops responding out of complete randomness and you see an error message popping up which says something like this:

0x00000050 (parameter1, parameter2, parameter3, parameter4)

Solution

Error Causes

The stop error 0x00000050 signifies that there’s a PAGE_FAULT_IN_NONPAGED_AREA problem. If you’ve seen this error on different occasions then you will find the parameters in the message to be varying. That is because they are dependent on your PC’s configuration. Not all Stop errors "0x00000050” occur due to a single issue.

However, the most common problem which is encountered which results in the stop error popping up is due to a pool corruption occurring in the Srvnet.sys file.

This issue might be caused because of software incompatibility or a defective physical memory which resulted in requests for data for a hardware driver or service which was not found in the memory.

If you find the error occurring after you’ve installed a new application or a device driver then you should access Safe Mode and uninstall, disable or remove that application or driver.

Further Information and Manual Repair

In order to fix this issue, you should try booting your computer to the “Last Known-Good Configuration” as listed during startup.

For this you have to follow the below-mentioned steps:

1. Start your system.
2. When you see the message which says “For Troubleshooting And Advanced Startup Options For Windows, Press F8” hit F8 and proceed.
3. Use the up and down arrow keys to highlight “Last Known-Good Configuration” and hit enter (This method will only work if your system boot was not successfully carried out ever since you made any specific changes).
4. When you are starting the computer, press F12 and proceed with the PSA/32 Bit Diagnostics.
5. Do the following so that a clean boot can be performed:

• Go to the Start menu when the Windows 7 desktop shows up.
• On the search bar, type “msconfig” and hit search.
• Disable all the applications which are listed on the “Startup” tab.
• Now head over to the “Services” tab and mark the option which reads "Hide all Microsoft Service".
• Select the “Disable All Services” option.
• Apply the changes by clicking on “Apply” then restart your PC. You should now check the performance of your computer. If you don’t see a BSOD then you start re-enabling all the Services and Startup applications one by one until you finally figure out which one is causing the BSOD to appear.

6. Update your Windows with “Windows Updates”.

If you suddenly find the Windows Recovery Environment not working and you see an error message saying, “Could not find the recovery environment”, then you’ve come to the right place as this post will guide you on how you can fix it. In times when you can’t boot into the Windows Recovery Environment, there could be several reasons behind it. However, have you ever wondered where exactly the Windows Recovery Environment is in your computer? Windows initially places the Windows RE Image file in the installation partition during Windows Setup so if you have installed Windows in the C drive, you can find the Windows RE at the C:/Windows/System32/Recovery or C:/Recovery folder. Keep in mind that this folder is hidden and later on, the system copies the image file into the recovery tools partition to make sure that one can boot into recovery if there are any issues with the drive partition. The “Could not find the recovery environment” error mostly occurs if the Windows Recovery Environment is disabled or if the “Winre.wim” file is corrupted. Thus, to fix this error, you need to refer to the given suggestions below.

Option 1 – Try to enable Windows Recovery Environment

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• Next, type the “reagentc /info” command and tap Enter to execute it.
• After that, if the output states that Status is enabled, then you’re all set.
• Now type the “reagentc /enable” command and tap Enter to enable the Windows Recovery Environment. You will see a success message at the end signifying that Windows RE is available.

Option 2 – Try to fix the corrupted or missing “Winre.wim” file

If the Winre.wim file is either corrupted or missing, you need to get a new copy of this file from another computer where the Windows RE is working. Once you’re able to get a new copy of the Winre.wim file, you have to set the image path to a new location. For more details, refer to these steps:

• First, type “Powershell” in Windows Start Search and right-click on Windows PowerShell from the results, and select Run as administrator.
• Next, execute the given command below to change the path of the WIM file to the new location. Note that the steps should be used when the file path of the Windows Recovery Environment is different from the usual spot.

Reagentc /setreimage /path C:RecoveryWindowsRE

• As mentioned, if the file is corrupted, you just have to get a new copy from another PC but before you do that, make sure that the WINRE on that computer is disabled (just enable it later on) and then place it in the C:/Recovery path and then set its path again using the command given above and then verify its path by executing the following command.

reagentc /info command

Note: Since the Recovery folder is hidden as well as the WINRE folder in it and you won’t be able to access them using the Windows File Explorer, you need to use the Windows PowerShell or Command Prompt so that you can access them.

Option 3 – Try checking and fixing the WinRE Reference in the Windows Boot Loader

The Windows Boot Loader is the one that determines if it has to load the Windows Recovery Environment. It could be that the boot loader is pointing to an incorrect location which is why you’re getting the error. To resolve it, you have to check and fix the WinRE Reference in the boot loader. How? Follow these steps:

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• After that, execute the “bcdedit /enum all” command.
• Next, look for an entry in the Windows Boot Loader identifier set as Current and look for “recoverysequence” in that section and take note of the GUID.
• Ensure that the device and the osdevice items show the path for the Winre.wim file and that they are the same. If not, you need to point the current identifier to the one which has the same.
• Once you’ve found the new GUID, execute this command: bcdedit /set {current} recoverysequence {GUID_which_has_same_path_of_device_and_device}
• Now check if the error in the Recovery Environment is fixed or not.

Option 4 – Try creating a Recovery Media

You could also try creating a Recovery Media to resolve the error in the Windows RE. All you have to do is download the Windows 10 ISO file using the Media Creation tool and then create a recovery drive. Once you’re done, check if it fixes the problem or not.

If you are trying to run Windows Upgrade on your Windows 10 computer but suddenly interrupted by the error 0x800F081E – 0x20003, worry not for this post will guide you on how you can fix this Windows Upgrade error. This particular Windows Upgrade error is a Windows status code for CBS_E_NOT_APPLICABLE which indicates that some of the update requirements are missing or the files that are installed are already of a higher version compared to the ones that are still pending. In most cases, this error occurs when you try to upgrade to earlier versions of the Windows 10 N edition to a later version. Here’s the full content of the error message:

“0x800f081E-0x20003, The installation failed in the SECOND_BOOT phase with an error during BOOT operation”

In case you don’t know, Microsoft distributes special “N” editions of Windows in Europe and the “KN” editions in Korea. These editions are the same as the standard editions of Windows except that they do not have the Windows Media Player as well as the multimedia playback features. Thus, when the Windows Upgrade fails with the error code and error message and it doesn’t provide much information as to why the update couldn’t be installed, there is something you can do about it to fix the error. Since Windows uses generic error codes and so if you see the error code 0x800f081e, you have to check the error log first. For more details, follow the instructions laid out below. Step_1: You need to navigate to C:$WINDOWS.~BTSourcesPanther and from there look for the text file named “setuperr.log” and open it with a text viewer/editor program like Notepad. Step_2: After opening the setuperr.log file, you should see content that’s similar to this:

C:WINDOWSSoftwareDistributionDownload80b2677d6e15a2a206625bb25a7124feamd64_Microsoft-Windows-MediaPlayer-Package~~AMD64~~10.0.17134.1. Error: 0x800F081E 2019-09-10 20:26:57, Error SP Operation failed: Add [1] package C:WINDOWSSoftwareDistributionDownload80b2677d6e15a2a206625bb25a7124feamd64_Microsoft-Windows-MediaPlayer-Package~~AMD64~~10.0.17134.1. Error: 0x800F081E[gle=0x000000b7]

Note: From the content above, it is clear that the Windows Upgrade failed due to complete due to the Windows Media Player. It could be that the log file may contain other error messages and other error codes and if you see the error code 0x800f081e from the list, then you need to uninstall the Media Feature Pack. Step_3: You have to uninstall the Media Feature Pack.

• Tap the Win + R keys to launch the Run dialog box and type “optionalfeatures.exe” in the field and hit Enter to open the Windows Features wizard.
• Next, you need to wait until the list of Windows Features populates and then click on the + sign to collapse the folder of the Media Features.
• After that, uncheck the “Windows Media Player” option from the Media Features folder.
• Now click on the Yes and OK buttons to save the changes made and then close the Windows Features dialog box.
• Restart your computer and boot, try to run the Windows Upgrade process again, and check if the error is fixed or not.

Note: If the installation has been successfully completed, you have to go back to the Windows Features and enable the Windows Media Player again. And if you are using the Windows 10 N Edition, then you can just download and install the latest version of the Media Feature Pack for your Windows 10 N edition. On the other hand, running the built-in Windows Update troubleshooter could also help you resolve any Windows Update-related problems, including the error 0x800F081E – 0x20003. 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.