5 Windows 10 Upgrade errors you might encounter

Error 1753 - What is it?

Error 1753 is an RPC endpoint mapper error code. This code is typically displayed as "EPT_S_NOT_REGISTERED" or sometimes as the hexadecimal value 0x6D9.  Error 1735 indicates that there are no more endpoints available from the endpoint mapper. To understand this better, basically, RPC is an inter-process communication (IPC) method. This is used by clients and servers for communication purposes. RPC is used by programs to execute programs on a server computer. The perfect example of this is Microsoft Outlook. You communicate with Microsoft Exchange Server using RPC. This enables you to send and receive emails. When you use Microsoft Outlook to send emails, your computer sends a message to the server computer in an obscure coding. The server responds to your computer with another message that contains the results of the executed program. This is all being carried at the backend of the running program. Integral to this is the endpoint. The endpoint includes the name, port, or a group of ports on a computer that is monitored by the server for incoming client requests. This is a network-specific address to be precise. The endpoint mapper is the part of the RPC subsystem that is responsible for dynamically assigning endpoints to the server. When this function fails it leads to error 1753 message display. It shows that RPC service is not available.

Solution

Error Causes

The error code 1753 indicating RPC endpoint mapper service failure is triggered due to multiple reasons. These include:

• Windows registry damage and corruption
• Malfunctioning of the hardware
• Spyware intrusion or viral infections
• Device driver conflicts

Further Information and Manual Repair

This error code may cause a great deal of inconvenience to execute programs that are dependent on the server. It can lower your productivity and performance. To avoid the hassle, it is advisable to repair the error 1753 immediately. The best way to resolve this error 1753 in seconds is to download Restoro. By using this repair tool, you can fix the error right away for free without paying hundreds of dollars to a professional expert. Restoro is a new and innovative PC fixer integrated with an automated algorithm and intuitive technology that enables users to sit back and relax while Restoro runs on the system and detects all PC-related issues in the shortest time. In just a few clicks you can resolve even the mightiest PC issues like the error code 1753 RPC endpoint mapper problem and resume back to the program in no time.

Why Restoro

It is efficient and user-friendly. Restoro can be used by users of all levels so even if this is your first experience using a repair tool, you don’t have to worry. To operate it, you don’t have to be a computer programmer or have sound technical expertise. It is simple and very easy to use. The layout is simple and neat complimented nicely with easy navigation and a sophisticated user interface. Restoro is a high and multi-functional error tool embedded with powerful, performance-driven, and value-adding utilities, all in one. So, whether the error code 1753 is triggered due to a viral infection on your system or registry corruption, you don’t have to look for different tools to resolve the error, simply run Restoro to fix the issue right away. Restoro includes a dynamic registry cleaner that detects all registry issues and wipes out the clutter from the hard disk like junk files, internet history, and invalid entries which is by the way the number cause for registry corruption leading to error 1753. It clears up disk space and RAM and repairs the misconfigured system files and corrupt registry in seconds thus resolving error 1753. Restoro also functions as a system optimizer thus boosting the speed and performance of your PC massively and reducing boot time. In addition to this, it also has a backup feature.  This tool is embedded for safety purposes. This feature enables you to create backup files on your PC before you start system repair. This helps you recover data in the event of data loss during system repair. To get started:

• Click here to download and install Restoro on your system
• After installation, run it to scan for errors like 1753
• Now press the repair tab to resolve

Logon.scr Application Error - What is it?

To understand Logon.scr application error, it is first important to understand the function of logon.scr. Logon.scr is an important file that is located in the Windows\System32 folder. It guarantees Windows systems stability. Logon.scr application error occurs when logon.scr file gets corrupt. It is a common system error that can happen in most Windows platforms. It usually pops up during system start-ups and when trying to launch certain programs. Some of the common systems of this error code include: system halt, freeze, no application icons are visible on the desktop, random blue screen of death and system performance decreases dramatically.

Solution

Error Causes

Two of the most common causes of logon.scr application error is:

• Corrupted and damaged logon.scr file
• Viral infection

It is advisable to fix this error code immediately because it leads to serious damages. It is fatal and can result in a system crash; therefore resolve it right away.

Further Information and Manual Repair

To resolve this issue on your computer you don’t have to spend hundreds of dollars to hire a professional for the job. The good news is that it can be repaired easily and does not require any technical expertise. Here are some of the most effective and easy DIY methods to resolve the error on your screens.

Method 1 - Replace the Damaged and the Corrupted Logon.scr File

Whether the file gets corrupted or is accidentally deleted, the best way to fix the issue is to download the Logon.scr file again from a reliable website and install in the following location C:\Windows\System32. Alternatively you can also get the file copy form another proper functioning computer by using flash drive if you don’t have an internet connection to download the logon.scr file online.

Method 2 - Restore Points by Applying System Restore of Windows

Another way to resolve this is to restore points to bring back your system to the previous state before the error occurred. To do this, simply click the start button and type ‘System Restore’. Now click System Restore in the result and click next. Select the restore point in the list and click the next button to proceed. To activate changes reboot your PC.

Method 3 - Scan and Remove Viruses

If Logon.scr application error still persists, then it could be due to viruses. To resolve, install a powerful anti-virus. Scan your entire PC and remove viruses.

Method 4 - Repair the Registry

Corrupt and damaged Logon.scr file also triggers issues with the registry. DLL files and other important files like Logon.scr application files may get damage due to too many bad and invalid registry entries. Registry stores all the activities performed on the PC including unnecessary files like junk files and cookies. If these are not removed timely, these files accumulate and corrupt important files. Therefore, to fix the error it is advisable to clean and repair the registry. The best way to go about is to download Restoro. This is a user-friendly and multi-functional PC Fixer deployed with a registry cleaner. It scans for all registry errors and removes all the invalid entries. It cleans the registry and repairs the damaged files thereby resolving the issue in seconds. Click here to download Restoro and resolve the Logon.scr application error now!

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 0xC004C4AE - What is it?

Activation errors in Windows 10 can interfere with your ability to fully use the system. When Error Code 0xC004C4AE appears on your computer, you may see a message that shows that the validation process has been stalled due to binaries that appear to have been tampered with.  

While the text of this message may sound intimidating to people who are not familiar with the inner workings of the Windows 10 system, the basic meaning of the error message is that something has been introduced to the system that is not natively supported in Windows 10. During the Activation process, Windows checks to ensure that all of the Windows elements that are currently on the computer are valid and authentic to the Windows system. Usually, this particular error code refers to a language package that has been downloaded into the system using an outside application, which the Windows 10 operating system does not support. 

Common symptoms include: 

• An error message when the activation is attempted 
• Inability to complete the Windows 10 Activation process 
• Inability to fully use apps in Windows 10 until the issue is resolved 

This particular error can easily be resolved with a few simple steps. However, if you are not confident in your ability to use the methods below or they do not fully remove the issue on your computer, you may want to seek the assistance of a qualified repair technician who is well versed in the Windows 10 Activation process.

Solution

Error Causes

The most basic cause of Error Code 0xC004C4AE is that an unsupported language package has been enabled in the computer. This most often occurs when third-party applications have been used to introduce additional display languages to your system. While third-party applications that provide language packs are acceptable in some versions of the Windows operating system, the Windows 10 Activation process will not be able to complete if the system detects that one of these unofficial language packs exists on your machine.

Further Information and Manual Repair

There are several methods that may be helpful in resolving the basic issue in the display languages that causes Error Code 0xC004C4AE to appear: 

Method 1: Restore Your System to an Earlier Point to Revert Changes 

Use a backup copy to restore your computer to an earlier date, in effect undoing the changes that caused the error. When your system has been restored, you will be able to go through any language packs that are not native to the Windows operating system and remove them before re-attempting the installation and activation of the Windows 10 system. 

This method is most useful if you keep a regular backup of your system and files. If you do not regularly back up the information on your computer, attempt one of the other methods instead. If you are unsure of how to use a backup to revert your changes or are not comfortable completing this step on your own, contact a certified Windows technician to assist you in the process. 

Method 2:  Revert to an Earlier System to Remove the Language Pack 

If you are unable to restore your system using a backup, the other option to resolve Error Code 0xC004C4AE is to halt your installation of Windows 10 and go back to Windows 7 or Windows 8.1, from which you will be able to remove the language pack in question. Once the offending language pack has been completely removed from your computer, the Windows 10 Activation process should be able to proceed normally. 

Several versions of windows don’t support language packages, so the best way to prevent this error from occurring is to avoid using any kind of third-party tool to install additional languages onto your Windows system. Activities Language You may be able to use third-party tools to instead complete alternative language actions without installing these languages as language packs. 

If the above solutions do not help you to resolve Error Code 0xC004C4AE on your machine, get in touch with a qualified Windows repair technician, who may be able to perform the operations needed to remove the problematic language pack from your computer and allow the Windows 10 Activation process to continue to completion. 

Error Code 0xc004f050 – What is it?

Error code 0xc004f050 refers to a problem with activating the Windows key. The problem appears when you try to activate a copy of Windows by using Windows Activation wizard. This happens when the system becomes unstable and critical system files start missing. Though Windows 10 is a free upgrade for Windows 7/Windows 8/Windows 8.1 users, the activation error is still an issue. If you already had Windows 7/Windows 8/Windows 8.1 activated and did an upgrade successfully, then there should be no problem. This Problem Occurs only when you do a clean install.

Symptoms

When you try to activate a copy of Windows Vista or Windows 7 by using the Windows Activation wizard, you receive an error similar to the one below:

An error has occurred Code: 0xC004F050 Description: The Software Licensing Service reported that the product key is invalid

Solution

Error Causes

• This causes due to an invalid product key.
• This problem may occur if the license validity interval has expired, or if the license is not signed correctly.
• Error Code 0xc004f050 occurs when the system becomes unstable and critical system files start missing.
• Improper way of installing, deletion of some very important system files, misconfigured system files, etc. may also cause this error.
• When you do a clean install, it wipes everything from the Primary Drive and after the install, windows can't find the Hardware ID which is used to verify your license.
• For Windows 7, Windows Server 2008, and Windows Vista-based computers, this error may occur if you have entered the key for a beta version of the operating system while using the released version of the operating system.

Further Information and Manual Repair

This error is not something that can be fixed in seconds but will require some time and technical knowledge.

Method 1:

Re-insert the product key by using the Change Product Key tool:

1. Click Start, click Computer, and then click System properties on the toolbar.
2. In the Windows activation section, click Change product key.
3. If you are prompted for an administrator password, type the password or click Continue.
4. In the Product key box, type the product key, and then click Next.
5. Follow the steps in the Windows Activation Wizard to complete the activation process.

Method 2:

Activate Windows by using the automated telephone system:

1. Click Start, and then click Computer.
2. Click System properties on the toolbar, and then click Click here to activate Windows now in the Windows activation
3. If you are prompted for an administrative password, type it and click Continue.
4. Click Show me other ways to Activate.
5. Click Use the automated phone system and follow the instructions.

Method 3:

1. Clean install Windows 7/Windows 8/Windows 8.1 using the installation disk and activate your copy.
2. Now, download all the updates to see the Windows 10 Upgrade notification or download Windows Media Creation Tool and use the option Upgrade this PC to get Windows 10 right away.
3. Once the upgrade is done, check the Activation Status. It will be fully activated as it should be. The Error code 0xc004f050 should not appear anymore.

If you want to get rid of the old Windows installation folder, then use the Windows Media Creation Tool to create a Flash Drive. Clean Install Windows 10. Now, every time when it asks for a product key, skip it. After installation is complete, Windows will automatically identify and activate your Copy. NOTE: Clean Install will make Sure you cannot roll back to your previous Windows 7 or Windows 8. So do it only if you are confident of using Windows 10 from here on. To verify the Windows activation status, follow these steps:

• Click the Start button, and then click Computer.
• Click System properties on the toolbar, and then view the activation status in the Windows activation section.

Did you know you can use emoji in file names inside Windows 10? It is no secret that emojis are basically everywhere and Microsoft has seen this and integrated them into Windows itself, so you can name files using emojis or combine them with text. Placing emojis in file names or in the text is extremely easy, all you have to do is press ⊞ WINDOWS + . and the emoji dialog will open from where you can find which emoji you would like to use. And that's it, you just used emoji for the file naming.

!!!NOTE!!!

In theory, some applications may not like these emojis if they don’t support Unicode characters. However, modern applications are designed to work with a broad set of languages that should properly support emojis. For example, the classic Windows Command Prompt can’t see emoji characters in file names properly, but both PowerShell and Microsoft’s new Windows Terminal can display them properly. If you do run into a problem, you can always open File Explorer and rename the affected files and folders to remove the emoji characters. You can then use those files in applications that don’t properly support emoji file names.

This post will guide you in fixing yet another annoying Blue Screen of Death error, “BUGCODE_USB_DRIVER”. This particular BSOD error occurs due to some issue with usbhub.sys, winusb.sys, or usbport.sys system driver file. When you encounter this kind of Stop error on your Windows 10 PC, it indicates that an error has occurred in the Universal Serial Bus or USB driver. The USB driver is issued by Microsoft themselves and it comes along with the Windows 10 system which is why it is difficult to download its latest version using a web browser. Thus, you need to take some basic steps to resolve the problem. Carefully follow the given fixes below to fix the BUGCODE_USB_DRIVER Blue Screen error and before you proceed, you need to create a System Restore Point, this way you have some backup in case something goes out of hand.

Option 1 – Update the USB Controller Drivers

• 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.
• Restart your PC and then click the “Search automatically for updated driver software” option.

You also have the option to update the motherboard and the USB driver from the manufacturer’s official website.

Option 2 – Check for any available Windows Updates

Another you can try is to check if there are any Windows Updates available to make sure that your Windows 10 PC has all the latest updates installed. All you have to do is go to Settings > Update &security. From there, just click on the Check for updates button.

Option 3 – Uninstall conflicting programs and services

There are certain programs like VMWare, Virtual Box, Hyper-V Virtualization services that might be in conflict with the USB port drivers on the parent operating system. Thus, you can try uninstalling the aforementioned programs and other similar ones to see if it fixes the BSOD error.

• 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. If uninstalling the programs mentioned above didn’t help, you might want to try putting your PC in a Clean Boot State to help you find the faulty program.

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

Option 4 – Modify the Power Settings

• In the Cortana Search box, type “power options” and then select Power Options from the search results.
• After opening Power Options, click on Change plan settings for your selected power plan.
• Next, click on Change advanced power settings.
• Then look for USB Settings and click on it to expand it.
• Now expand the USB selective suspend setting and then disable it.
• After that, click on the Apply and then OK buttons to save the changes made.

Option 5 – Check for any hard disk errors

• On your desktop, right-click on the “This PC” or computer icon and then select Manage to open the Disk Management. Here you get to check your drive’s health.
• Next, click on Disk Management on the left side panel.
• From there, check the state of your drives. If it shows that all your partitions are healthy then it means all is good and that the problem may have something to do with some physical issues with your hard drive.

You might also want to run the CHKDSK utility to help you fix any issues with your hard disk. 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 following command and hit Enter:

chkdsk /f /r

• Wait for the process to be completed and then restart your computer.

The Blue Screen of Death error or BSOD is definitely not an issue to face on your computer. Many users, if not all, have already experienced this headache at least once. One of these BSOD errors is the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error. The bug check error code for this is 0x000000FC and is usually caused by outdated or faulty drivers. In some cases, it could also be caused by an error in the Random Access Memory or RAM. This kind of error in the RAM might be physical, based on drivers, or even some kind of unwanted malware. So basically there are lots of possibilities why this particular BSOD error pops up. If you are currently facing this BSOD error, read on and carefully follow the suggestions given below but before you do that, make sure to create a System Restore point just in case something goes wrong. This way, you can always undo those changes using the System Restore point. Once you have that covered, proceed to the options given below to fix the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error.

Option 1 – Try updating Windows 10 with all the security patches and updates

You might be able to fix the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error by simply updating your Windows 10 computer with all the security patches and updates. To do so, go to Settings then proceed to the Windows Update section > Update & Security > Windows Update, and then click on the Check for Updates option. After you do that, it will automatically find and install all the latest security patches and feature updates from Microsoft.

Option 2 – Try updating all your drivers

From time to time, drivers get corrupted or outdated so it’s no surprise that they conflict with the operating system and cause errors like the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY BSOD error. To fix the problem, you need to update all your drivers. Follow the steps below to update your 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. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. 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.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it.

Option 3 – Try running a Memory Check using Windows Memory Diagnostic

As mentioned, this error might be caused by some issues in the memory. To resolve it, you need to run the Memory Check on your Windows 10 PC. Refer to these steps to do so.

• Tap the Win + R keys to open the Run dialog box.
• Then type “mdsched.exe” in the field and hit Enter to open the Windows 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 4 – Try using the System File Checker via Command Prompt

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 ATTEMPTED EXECUTE OF NOEXECUTE MEMORY BSOD error. 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.

Error Code 0x80004002 - What is it?

Error Code 0x80004002 is a Windows-based error code that affects Windows 10 and previous operating systems, including Windows XP, Vista, Windows 7, and Windows 8. In most instances, the message box that shows Error Code 0x80004002 pops up as you attempt to install new software or programs on your machine.

Common symptoms include:

• Problems running programs that once worked
• Slow response time of your computer to commands entered with the keyboard or mouse
• Trouble shutting down or starting up your machine
• Error message regarding your registry, updates, or response time.

There are a number of different solutions that you can use to attempt to resolve Error Code 0x80004002. Because there are multiple causes to the issue, some of the methods used to successfully address the problems at hand are fairly simple, while others require advanced knowledge or abilities to complete. If the methods below are not successful in the resolution of the issue or if you aren’t confident in your skills to implement these methods, contact a qualified Windows repair technician to assist you. Once this error message is not rectified, you could be exposing your computer to other error messages, including error code 0x80240020.

Solution

Error Causes

There are many different issues that can contribute to the appearance of Error Code 0x80004002. The most common causes for this particular error message include:

• Errors in registry files
• Missing system files that have accidentally been associated with other programs and deleted
• Viruses or malware that cause corruption in program or system files
• Installations that have failed to complete fully

Further Information and Manual Repair

Due to the number of causes that can contribute to Error Code 0x80004002, there are a number of methods that you can use to attempt to resolve the issues behind the error. While some of these methods are fairly easy to implement, others may require you to use programs like registry cleaners and driver installation wizards, so if you are not comfortable using these kinds of software, contact a certified Windows repair technician to assist you.

Here are the top ways that you can attempt to address Error Code 0x80004002:

Method One:  Run Your Windows Registry Cleaner

Many different registry cleaning tools exist on the Internet, but not all of these are provided by trustworthy sources. Rather than trusting a file from an unknown publisher, you can use the registry cleaning program included in your Windows software package.

Run this tool to complete a scan of your files, discovering which ones may need to be repaired. In most cases, the registry cleaner itself can repair the necessary files and resolve the error.

It is always a good idea to restart your computer after you have run the registry cleaning tool to ensure that your machine can accurately assess the newly repaired files.

Method Two:  Update Your Drivers and Software

In some cases, Error Code 0x80004002 arises when drivers are out of date. If you believe that this is the case, you can check on the status of your various drivers by going into the settings for your operating system and selecting the “Update Drivers” option.

You can also check your system for any necessary updates to your Windows software, which may serve to address the error code.

After you have checked and installed any necessary drivers, make sure to restart your computer to fully apply any changes that the installation process has introduced.

Method Three:  Reinstall Your Windows Software

In some cases, the best way to address the missing or corrupt files that can cause Error Code 0x80004002 is to simply reinstall your copy of Windows. Always make sure to back up your files before reinstalling your software.

Method Four:  Run Your Virus Scan Software

Because Error Code 0x80004002 can also be caused by malware or a virus, you can run your virus scan software to detect and resolve the problem. After doing so, run the registry repair tool to fix any affected files and restart your computer.

Method Five: Use 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.

As you know, the Windows Media Creation Tool is a great utility in Windows that helps lots of users in installing Windows on their PCs. However, just like any other program in Windows, it also experiences a couple of issues every now and then. So in this post, you will be guided on how you can resolve a particular issue in the Media Creation Tool which is the error 0x80042405-0xA001A. You can encounter this error while creating a USB installation media used in installing Windows 10. When getting this kind of error in the Windows Media Creation Tool, you will see the following error message on your screen:

“We’re not sure what happened, but we’re unable to run this tool on your PC, Error code 0x80042405 – 0xA001A”

The error 0x80042405 – 0xA001A occurs while creating a bootable USB installation drive. This is a common error faced by many users and it has something to do with the USB hardware. To get this issue fixed, here are some suggestions you could check out.

Option 1 – Try to reformat the USB drive

Reformatting your USB drive might help in fixing error 0x80042405 – 0xA001A.

• Open This PC and right-click your USB drive from there then select Format.
• Next, select FAT32 as the drive type and uncheck the “Quick Format” option.
• After that, try to run the Windows Media Creation Tool again and check if the error is fixed or not. But hopefully, it should work since formatting the drive as FAT32 will give the driver a proper type and would resolve any minor issues in the drive.

Option 2 – Copy the Windows Media Creation Tool to the USB drive

If the first option didn’t work, you might want to copy the latest version of the Media Creation Tool to the USB drive. After you do that, you can run it from inside the drive. This is actually a working fix and can definitely get the USB drive to run with Windows inside it so it should resolve the error 0x80042405 – 0xA001A on the Windows Media Creation Tool.

Option 3 – Run CHKDSK to check the drive for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system including the “Diskpart failed to clear disk attributes” error.

• Tap the Win + S keys to open the Search box.
• Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• After opening an elevated command prompt, copy and paste the following command and hit Enter:

CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]

Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.

• Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
• If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
• After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
• Wait until the process is completed and then restart your computer.

Option 4 – Try checking the hardware components

On the other hand, it is also possible that the issue has something to do with a hardware problem and so you need to check the hardware components on your computer to determine that.