How to Fix DISM Error 1726 in Windows 10

There are some new generation motherboards for laptops and PCs that bring in support for both the Unified Extensible Firmware Interface or UEFI as well as the Basic Input Output System or BIOS. The main advantage of UEFI over the traditional BIOS is the fact that UEFI supports a hard drive that has a capacity of more than 2 terabytes. However, the disadvantage of UEFI is that it only supports the x64 Windows operating system versions and that the hard drive is supposed to use the GPT structure. So if your PC is compatible with and supports UEFI and you want to change from Legacy to UEFI, then you’ve come to the right place as this post will guide you on how you can exactly do that without having to reinstall it. There are two ways to change Legacy to UEFI. You can convert MBR to GPT using either the built-in utilities in Windows or using the Recovery Environment. Before you proceed, make sure that your computer fulfills the following prerequisites:

• Your PC’s motherboard should support both Legacy and UEFI.
• Your PC should be running at least the 1703 Windows 10 version or newer on an MBR partition.

Once you’ve made sure that your computer covers the aforementioned prerequisites, refer to the given options below.

Option 1 – Convert MBR to GPT via Windows built-in utilities

• In the Windows Search box, type “command prompt” and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After that, execute this command: exe /convert /allowfullOS
• Now, wait until the process is completed since you can track its process on your screen.
• Once it’s done, go to Settings > Update & Security > Advanced Startup options and from there, click on Restart Now. This will restart your computer and give you advanced options.
• Next, select Troubleshoot > Advanced Options where you will see further options including System Restore, Startup Repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• Now select the UEFI Firmware Settings. This will take you to the BIOS. Boot Mode is typically available under Boot > Boot Configuration. Once you’re there, set it to UEFI and then save the changes you’ve made. After that, your computer will restart.

Option 2 – Convert MBR to GPT via the Recovery Environment

• When the message appears on your screen while running Windows Setup, you need to tap the Shift + F10 keys to open Command Prompt.
• Make sure to run Command Prompt as admin and then execute this command: exe /convert
• After that, wait until the process is completed. When it’s done, you have to go to the BIOS just like in the first given option above.
• As mentioned, you can usually find the Boot Mode under Boot > Boot Configuration. Once you’re there, set it to UEFI.
• Now save the changes made and exit as your computer will restart.

The quickest and easiest way to log into your computer is when you use the PIN feature in Windows 10. Even though it is a bit slower compared to biometric logins such as Fingerprint and Iris scanning that comes under Windows Hello, the PIN feature is definitely less complicated. However, just like any other module of the software, it is also prone to some errors. In this post, you will be guided in fixing several PIN errors such as 0xd00000e5, 0x8007139f, and 0x8009003. These errors could be caused at different points in time like when you change or create a PIN or when you log into your computer. To fix the 0xd00000e5, 0x8007139f and 0x8009003 PIN errors, there are various solutions you can try. You may empty the contents of the NGC folder or remove and change the PIN or the password. You could also use the Group Policy Editor or reset the ACLs in the NGC folder as well as run built-in tools like System File Checker and the DISM tool.

Option 1 – Take ownership of the NGC folder and delete its contents

• Boot your computer first into Safe Mode.
• Next, you need to take ownership of the Ngc folder first and you can do that using Command Prompt.
• 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 C:WindowsServiceProfilesLocalServiceAppDataLocalMicrosoftNgc
• Note that the <path> is the location of the folder or file in File Explorer.
• Now type and enter this second command: ICACLS C:WindowsServiceProfilesLocalServiceAppDataLocalMicrosoftNgc /grant administrators:F
• Finally, once the command has been executed, restart your computer.
• Once your computer has restarted, delete all the contents in the Ngc folder and check if the error is now fixed.

Option 2 – Try to remove and change the PIN or password

The 0xd00000e5, 0x8007139f, and 0x8009003 PIN errors could be caused by some conflicting issues with the PIN or password you have set for the User Account of your computer. Thus, you have to remove or change the PIN or password to fix these PIN errors.

• Remove the PIN by going to Settings > Accounts > Sign-in options.
• From there, go to the PIN section and click on the Remove button.
• You will be asked to verify your account to proceed in removing the PIN, enter your credentials.
• Restart your computer and then set up a new PIN.
• Once you’re done, restart your computer and check if the error is gone now.

Option 3 – Try to use the Group Policy Editor

• Tap the Win + R keys to open the Run utility and type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Next, navigate to this policy setting: Computer Configuration > Administrative Templates > System > Logon
• After that, double click on the “Turn on convenience PIN Sign-in” option located on the right-side panel.
• Then set its radio button to Enabled. You will see the following description when you do so:

“This policy setting allows you to control whether a domain user can sign in using a convenience PIN. If you enable this policy setting, a domain user can set up and sign in with a convenience PIN. If you disable or don’t configure this policy setting, a domain user can’t set up and use a convenience PIN. Note: The user’s domain password will be cached in the system vault when using this feature. To configure Windows Hello for Business, use the Administrative Template policies under Windows Hello for Business.”

• After setting the radio button to Enabled, it will turn on the Logins in your computer using the PIN.
• Close the Group Policy Editor and restart your computer for the changes to take effect.

Option 4 – Try to reset the ACLs in the Ngc folder

• Type “command prompt” in the Windows Search bar and then right-click on the relevant search result and select “Run as administrator”.
• After opening Command Prompt with admin privileges, execute this command: C:/Windows/Service/Profiles/Local/Service/AppData/Local/MicrosoftNgc /T /Q /C /RESET
• The command you entered will start checking for errors and fix them automatically.

Option 5 – Run the System File Checker scan and the DISM tool

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

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.

• Now restart your computer.

DISM tool:

• Open Command Prompt.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-image /Restorehealth
• After that, wait until the process is finished and do not close the window as the process will probably take a couple of minutes.
• Once it’s done, restart your computer.

What is Mastodon? Mastodon is an open-source microblogging network very similar to Twitter. You can make 500 characters post messages called toot (tweet), share videos or images, and follow other people. But unlike Twitter, Mastodon is decentralized, meaning the entire Mastodon is not run by a single company pulling all strings.

Mastodon can be used directly in your web browser or through a mobile client on a smartphone or tablet. It includes features that seem copied from Twitter-like replies, boosts (retweets), favorites (loves), a timeline view, blocking, and voluntary content warnings that hide sensitive content.

Mastodon also has some great features that Twitter does not have like automated post deletion for the older post of a certain age, requiring approval for follows without restricting your account, and opting out of search engine indexing.

Currently, there are also no ads on Mastodon meaning no ad tracking or ad network surveillance.

How Does Mastodon Work?

Mastodon is a social media network made of nodes called servers or instances each running special software meaning anyone can run their own Mastodon instance (if they have a proper dedicated server). When you have your own instance it can be linked in the federation or remain private, so individuals or companies can have control over individual Mastodon servers.

The software itself is open source based on the social networking protocol ActivityPub which was developed by WWW Consortium.

While using Mastodon, people sign up for accounts with specific instances. Once logged in, you can view a local timeline (of posts from that instance only) or, if the instance is federated with others, see a federated timeline comprised of toots from people in other instances. Mastodon users can send messages to each other using their Mastodon account names that are similar to email addresses in that they feature the server address as well as the user name.

USB devices are one of the commonly used devices every day – from plugging mobile devices for charging using pen drives, you are making use of USB drives. However, there are times when you might encounter an error message saying, “Unknown USB Device” as you plug your USB device on your Windows 10 computer. So if you encounter this kind of error message followed by either of the following explanations, read on as this post will give you a couple of suggestions you can check out to resolve the issue.

• Device Descriptor Request Failed
• Port reset failed
• The device failed enumeration
• Set address failed
• Error code 43

You can fix this error using several ways. You can try changing the Power Options, update or roll back the USB drivers, turn off Fast Startup, or run the USB troubleshooter. Follow the options given below for more details.

Option 1 – Try to change the Power Options

• Tap the Win + R keys to open the Run utility.
• Then type “powercfg.cpl” and tap Enter to open the Power Options window.
• Next, go to your selected power plan and click the “Change plan settings” option to open a new page.
• From there, click on the “Change advanced power settings” option. This will open a new window where you can see various power consumption options.
• Now look for the USB Settings option and expand it.
• Then set the USB selective suspend setting to “Disabled” for both scenarios: On Battery and Plugged in.
• After that, click on OK and restart your computer to apply the changes made.

Option 2 – Update or reinstall the Universal Serial Bus Controller driver

Since it could be a driver issue, you can try to update or reinstall the Universal Serial Bus Controller drivers using the Device Manager. Refer to the following steps:

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.

Note: If it is a regular USB drive, then it will be listed as a USB Mass Storage Device but if you have a USB 3.0 device, then look for a USB 3.0 Extensible Host Controller.

• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 3 – Try turning off Fast Startup

• Tap the Win + R keys to open the Run dialog box and type in “control” to open the Control Panel.
• Next, click on the Hardware and Sound section and click on Power Options.
• Afterwards, select the “Choose what the power buttons do” option from the left side menu pane.
• Now click on Change settings that are currently unavailable and uncheck the entry that says, “Turn on fast startup (Recommended).
• Then click on Save Changes and restart your computer and see if it has fixed the problem or not.

Option 4 – Run the Hardware and Devices Troubleshooters

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

A couple of Windows 10 users have reported an error on domain-connected systems when they tried accessing their computer systems remotely. This occurs when the network level authentication or NLA is enabled on the computer. If you are one of these users, you better keep reading as this post will guide you on how you can fix this error. To resolve this issue, there are several workarounds you can try. You can either disable this option directly via properties or you can also modify some registry entries or sub-keys and restart the system. When you encounter this problem, an error message pops up that states:

“The remote computer that you are trying to connect to requires network level authentication (NLA), but your windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.”

Or you could also see this error message instead:

“The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support.”

Before you proceed in troubleshooting the problem using the options provided below, you need to create a backup for your data or system restore point as well as make a copy of any registry entries you are going to modify.

Option 1 – Disable Network Level Authentication via Properties

The NLA is a useful tool that provides your computer with extra security and helps network administrators in controlling who can log into the system with just a click of a single box. However, there are times when it can become a disadvantage and could prevent you from accessing your system remotely. Thus, you need to disable it using Properties.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” and tap Enter to open System Properties.
• Next, go to the remote tab and uncheck the checkbox for the “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” option.
• Now click the Apply button to save the changes made and exit System Properties and then try logging into the remote computer again and see if the problem is fixed or not.

Option 2 – Disable NLA via Registry Editor

Note that you can only use this option if the first one didn’t work for you. Take note that this option will require you to restart your PC completely which could mean some downtime if your computer is running a production server. So make sure to save all your work.

• Tap the Win + R keys to open the Run dialog box and then type in “Regedit” in the field and tap Enter to open the Registry Editor.
• From there, click on File > Connect Network Registry and input the details of the remote computer and then try to connect.
• Navigate to the path below after you’re connected:

HKLM >SYSTEM > CurrentControlSet > Control >Terminal Server > WinStations > RDP-Tcp

• After that, change the values given below to “0”
  • SecurityLayer
  • UserAuthentication
• The navigate to PowerShell and execute this command – restart-computer

Option 3 – Disable NLA via PowerShell

PowerShell allows you to tap into the remote computer and once you’ve targeted the machine, you can execute the commands given below to disable NLA.

• Tap the Win + S to open Search and then type in “PowerShell” in the field. Right-click on the related result and select the “Run as administrator” option.
• After opening PowerShell, execute the command below:

2. Once in the PowerShell, execute the following command:

$TargetMachine = “Target-Machine-Name” (Get-WmiObject -class “Win32_TSGeneralSetting” -Namespace rootcimv2terminalservices -ComputerName $TargetMachine -Filter “TerminalName=’RDP-tcp'”).SetUserAuthenticationRequired(0) Note: In the command given, the “Target-Machine-Name” is the name of the machine you are targeting.

Option 4 – Use the Group Policy Editor to disable NLA

Another option you can use to disable NLA is via the Group Policy Editor. This is ideal for you if you are blanket disabling. Just take note that the Group Policy Editor is a powerful tool and that if you make some mistakes by changing values you have no clue about, you can render your computer useless so make sure that you create a backup for all the values before you proceed.

• Tap the Win + R keys to open the Run dialog box.
• Then type in “gpedit.msc” and tap Enter to open the Group Policy Editor.
• From there, go to this path – Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
• After that, search for “Require user authentication for remote connections by using Network Level Authentication” and set it to disabled.
• Now check if the error is fixed or not.

Windows 10 has displayed one of the most efficient and user-friendly interfaces. However there have been many issues on the backend of this commonly praised operating system: For example, Windows Update is still a wonky and error-laded system application. One example of this error is Windows Update Error 0x80073712 which stands in the way of users just wanting to keep their PCs updated hassle-free. The error code 0x80073712 signifies that a file needed by Windows Update to function is either damaged, missing, or corrupted. However, this does not mean that your Windows version will forever stay as-is with no mode to update it. Windows Update Error 0x80073712 is perfectly fixable with the set of provided steps below and some of Windows’ built-in troubleshooting steps:

Solution 1: Open Windows Update Troubleshooter

1. Open the Windows Update Troubleshooter by pressing the Windows and S keys simultaneously.
2. Enter the word “Troubleshoot” in the search box and select the Troubleshoot result
3. On the new window, select “Windows Update” to troubleshoot.
4. Run the troubleshooter, then open Windows Update and try to install the update again.

Solution 2: Run the DISM tool

1. Open the command prompt by pressing Windows and S keys simultaneously
2. Enter “cmd” in the search box. Right Click command prompt among the results and select “Run as administrator”
3. In the Command Prompt window type the following and press the Enter key after every command

DISM.exe /Online /Cleanup-image /Scanhealth DISM.exe /Online /Cleanup-image /Restorehealth

4. To close the Administrator: Command prompt window, type Exit, and then press Enter.
5. Run Windows Update again.

Solution 3: Rename the Software Distribution folder

1. Open the command prompt as previously mentioned
2. Input the following command pressing Enter after every line net stop wuauserv net stop cryptSvc net stop bits net stop msiserver rename c:/windows/SoftwareDistribution/softwaredistribution.old net start wuauserv net start cryptSvc net start bits net start msiserver exit
3. Restart the PC and run the updater if it works again.

Solution 4: Restart Windows Update Services

1. Press the Windows logo key and R together to open Run -> Input services.msc -> and press Enter
2. Search for the Windows Update service -> Check its status
3. If it is not indicated, right-click on the service and select Start to force start your Windows Update
4. If you see an error, locate the Startup Type option and set it to Automatic
5. Now you should reboot your computer and see if your Windows Update is OK

Solution 5: Fix Registry Issues

If after all the aforementioned solutions, you still experience problems with Windows Update, the problem may lie in the registry that is either damaged or corrupted. You may choose to do manual editing of your Windows registry by opening your Windows registry editor. But doing so is risky as one wrong letter may do incalculable damage to your system. To do so safely for more inexperienced users we recommend using a third-party registry cleaner/tools, many of which can be found online.

There are instances when instead of fixing problems the Windows Update brings you problems on your Windows 10 computer. You might even see some pending Windows Updates which for some reason, refuse to install no matter what you do. The good thing is you won’t have to deal with those failed and pending updates that are incompletely downloaded to your PC as you can actually delete them. Follow the instructions prepared below to delete the failed and pending Windows Updates.

Step 1: The first thing you have to do is delete all the contents in the Temporary folder

• Tap the Win + R keys to open the Run dialog box.
• Next, type in “%temp%” in the field and hit Enter or click OK to open the Temporary folder.
• From there, select all the folders and files within the Temporary folder and then delete them all.

Note: %temp% is one of the many environment variables in Windows that could open the designated folder by Windows as the Temporary folder which is usually located at C:\Users[username]AppDataLocalTemp.

Step 2: Next, remove the pending.xml file

• Go to the C:\Windows WinSxS folder.
• Once you’ve opened the folder, look for a file named “pending.xml” file and right-click on it and you can either rename it or delete it.
• After that, the Windows Update should delete the pending tasks and build a fresh new update.

Step 3: Delete all the contents of the SoftwareDistribution folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• Next, got to the C:\Windows\Software\Distribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Step 4: Try resetting the catroot2 folder

You can also try resetting the catroort2 folder as it is known to fix tons of Windows Update issues. Both the Catroot and catroot2 are Windows operating system folders that are required for the Windows update process.  So when you run the Windows Update, the catroort2 folders stores the signatures of the Windows Update package and helps it in the installation. It makes use of the “%windir%System32catroot2edb.log” file in the updating process. Afterward, the updates are stored in the SoftwareDistribution folder which is used then by the Automatic Updates in order to execute the updating process. Keep in mind that you must not rename or delete the Catroot folder. Although the Catroot2 folder is recreated automatically by Windows, the Catroot folder isn’t.

What is Mapi32.dll Outlook Error?

Mapi32.dll is a Windows Messaging Application Programming Interface that enables Windows to perform various email functions and launch messaging programs like Microsoft Outlook and Microsoft Office. The inability of the interface to execute email functions properly results in the Mapi32.dll Outlook Error. This error occurs mostly when you are attempting to upgrade the operating system to a new version.

Solution

Error Causes

The common causes of the Mapi32.dll Outlook Error during the OS upgrade are:

• Damaged or Corrupt Outlook user profile
• The software is overwritten by some other program
• Outlook PST file corruption

The Mapi32.dll Outlook Error message is displayed in either of the following forms:

• Mapi32.dll is missing
• Cannot start Microsoft Office Outlook. Mapi32.dll is corrupt or the wrong version.
• Mapi32.dll was not found
• Mail is not installed

Further Information and Manual Repair

So, what if you experience this issue and how do you fix it? Well, first there is no need to panic as Microsoft has recognized this issue and provided adequate solutions to fix this problem in no time. However, to ensure the Mapi32.dll Outlook error is a quick fix, you must first understand the cause of the issue and the message displayed on the screen.

1. Let’s say the errors occur because your Outlook profile is corrupt. In this scenario, the best solution is to create a new Outlook profile. Regardless of whether you have Windows Vista or XP, to create your new Outlook profile, first, you will have to click on the Control Panel, then User Account, and then Mail. Once you click on the Mail tab, the mail set up dialog box will open. In this dialog box there will be a ‘Show Profiles’ tab, click and then click the Add tab that appears next. Now type the name for your new Outlook profile and then click ‘OK’. After that, add an email account to go with the profile.
2. If Mapi32.dll is missing or corrupt, you will have to run ‘Fixmapi.exe’ to resolve the problem. It is located in the System32 folder inside the Windows directory in Windows Explorer.

• Therefore, first start Windows Explorer and then locate the following folder on your computer: C: /Program Files/Common Files/System/Msmapi1033
• Now find Fixmapi.exe and double click it
• After that locate the Mapi32.dll file and rename it to MSmapi32.old and press enter.
• Restart your computer when finished.

A word of advice for computer users is to scan for viruses with an antivirus program or a registry cleaner regularly to prevent the Mapi32.dll Outlook error from occurring in the first place. Viruses often latch onto .dll files and corrupt them. It’s always best to have a forward-looking approach.

Hello and welcome everyone, just a few years ago we had FLASH video content on the internet, we had FLASH games, full FLASH website experiences, and more, but then flash was shut down mostly due to security reasons meaning that in just a few months we have lost most of FLASH web content. However, there is still FLASH content on the internet even today, there are still FLASH videos and flash games, but we can not play any of that content since browsers do not support FLASH and you can not get the FLASH plugin for browsers. So what might be the solution for this situation?

Ruffle and FLASH emulation

Emulation of course. We will not be able to get the flash player working, well at least not the original and official one, but we can make flash content playable again inside our browsers. The first thing is first, we need to get an emulator package from the internet in order for this trick to work, one we will be using is RUFFLE. It is lightweight, it is free, it is open source and it is reliable, everything we need. Download RUFFLE from its official website here. For Chrome and Edge download the ZIP package, for Firefox, go to the Firefox section of the tutorial. There is also a desktop version of RUFFLE there so if you are keen on playing your flash content on your desktop computer you might well grab that as well, but for the sake of this tutorial where we are enabling flash in our browsers, we will not focus on that part since it is pretty straightforward. Now once you have downloaded the RUFFLE emulator, please extract it to the desired folder somewhere on your computer. Once it is extracted, start your browser of choice and follow instructions.

FOR CHROME:

1. Navigate to: chrome://extensions/
2. Turn ON developer mode in the top right corner
3. Click on Load unpacked
4. Navigate to the folder where you have extracted RUFFLE

FOR EDGE:

1. Navigate to: edge://extensions/
2. Turn ON developer mode on the bottom left corner
3. Navigate to the folder where you have extracted RUFFLE
4. Turn RUFFLE ON

FOR FIREFOX:

1. Go to the RUFFLE download page, we can not use the zip package we were using for Chrome and Edge
2. Right-click on the Firefox download link
3. Save link by clicking on Save link as...
4. Navigate to about: debugging
5. Click on this Firefox
6. Click Load Temporary Add-on
7. Select the .xpi that you have downloaded

BONUS:

If you want to enable FLASH content live on your website use:  <script src="path_to_ruffle/ruffle.js"></script>

If you encounter an error while trying to burn files to a CD or disk on your Windows 10 computer, stating, “Windows Media Player cannot burn some of the files”, read on as this post will guide you in fixing the error. Here’s the complete error message:

“Windows Media Player cannot burn some of the files. To investigate the problem, click the icon next to the files in the burn list.”

As you know, the Windows Media Player helps you burn songs or audio files to CD or disk but it does not always end up successfully as you could encounter some setbacks such as this particular error. Usually, this kind of issue occurs if an audio file does not comply with some restrictions so the Windows Media Player pops up this error instead. You can encounter this error message if:

• You include a file that’s not an audio file.
• If the total time limit exceeds 80 minutes (even though a CD has 700 MB storage capacity, you can’t burn audio of more than 80 minutes long)

To resolve the error, you have to remove the unsupported files from the burning list, change the burning speed or execute some tweaks in the Privacy settings. For more details, refer to the instructions provided below.

Option 1 – Get rid of the unsupported files from the burning list

You must get rid of the unsupported files from the list of files to burn. This list can be found on the right-hand side of the Windows Media Player. One of the indications that a file is causing problems is when there is a white cross in a red circle next to the file. You can simply click on that icon to remove the file from the burning list. Once you’ve gotten rid of all the unsupported files, try to burn your files to the CD or disk once more.

Option 2 – Try to modify the Privacy settings

In case you don’t know, the Windows Media Player comes with privacy settings that help you in various situations. However, on rare occasions, those settings could also trigger errors and this might be the one that’s causing the “Windows Media Player cannot burn some of the files” to pop up. Thus, you can try disabling these options to resolve the error. How? Refer to these steps:

• Open the Windows Media Player.
• Then go to Tools > Options. If you aren’t able to find the Tools menu, just tap the Ctrl + M keys. On the other hand, you can also tap the Alt key to display the menu options.
• Once you’ve opened the Options window, go to the Privacy tab where you can the “Enhanced Playback and Device Experience” section.
• In this section, you can find the following options. Make sure to disable them all.
  • Display media information from the Internet
  • Update music files by retrieving media info from the Internet
  • Download usage rights automatically when I play or sync a file
  • Automatically check if protected files need to be refreshed
  • Set clock on devices automatically

• After you disable the options listed above, click on the Apply and OK buttons to save the changes made and then try to burn the files again.

Option 3 – Try to change the burning speed

Since the burning speed is set to fastest by default, you can try to change the burning speed to resolve the problem. All you have to do is open the Options window and then go to the Burn tab. From there, select either Medium or Slow burning speed and save the changes made. Now try to burn your files to the CD or disk once again.