How to Fix Windows 10 Error 0x8000ffff

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.

If you’re suddenly unable to launch or open Google Chrome or unable to load web pages, then it’s most likely that the files in Chrome have been corrupted or some plugin is taking up a lot of resources which is why you encounter an error message saying, “Google Chrome has stopped working”. And when you try to check the Task Manager, you’ll see that Chrome is really taking up lots of resources, however, when you check the Taskbar, strangely, you will see nothing. If you are currently facing this issue in Chrome on your Windows 10 PC, follow the given options below.

Option 1 – Kill Google Chrome’s process in the Task Manager

If you aren’t able to open Chrome, then maybe its process is running in the background and you don’t see the browser windows. If that’s the case, you may have to force quit the browser and then try to open it again.

• First, right-click on the Taskbar then select the Task Manager. And if the Task Manager is not responding, you can just use the Alt + Ctrl + Del keys and then select the Task Manager.
• After opening the Task Manager, under Processes, look for Google Chrome’s process which would most likely be named “chrome.exe”.
• Right-click on Google Chrome’s process and then select the End task option.
• Now try to open Google Chrome again.

Option 2 – Try checking if your antivirus program is blocking Google Chrome

There are instances when due to false-positive, a security or antivirus program might block Chrome which is why it failed to open properly. Thus, you can just disable the security program temporarily and then check if you can now open Chrome or not.

Option 3 – Delete the User Profile in Chrome

You can also try deleting the User Profile folder in Chrome. To do so, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then copy and paste “%USERPROFILE%AppDataLocalGoogleChromeUser Data” and hit Enter.
• From there, look for a folder named “Default folder” and then copy the folder to another drive as a backup.
• After creating a copy of the folder, delete the Default folder.
• Next, open Google Chrome again and go to Settings > Advanced > Reset.

Option 4 – Disable the Extensions in Chrome

There are instances when issues on a browser are triggered or caused by some problematic extension. To find out which one of your extensions is causing the problem, disable them all first and then enable them back one by one.

• Click on the three-dotted icon for the menu located at the top-right corner of your screen.
• Then click on the More tools option and go to Extensions.
• From there, you will see a list of all the installed extensions in Chrome.
• Disable all these extensions and restart the browser.
• Now enable them back one by one to figure out which one of them is the culprit. You could also remove extensions that you no longer use.

Option 5 – Run the Chrome Cleanup tool

You might also want to try running the Malware Scanner & Cleanup tool in Chrome. This is a built-in tool that can help you get rid of any unwanted pop-ups, banners, ads, unusual startup pages, toolbars, and malware. Thus, it can help you to resolve the issue in Chrome.

Option 6 – Try to reinstall Chrome

If running the Malware Scanner & Cleanup tool in Chrome didn’t work out for you, you can try reinstalling it. To do so, follow these steps:

• Open the Settings app and go to System > Apps & features.
• From there, look for Chrome and uninstall it from your PC.
• Then go to the official website of Google Chrome and download its latest version and install it.

Error 0x8004210A - What is it?

0x8004210A is a typical POP3 email error message. This error may sometimes occur when you try to check your Post Office Protocol 3 (POP3) email account. 0x8004210A error code hampers your ability to both send and receive e-mails on your Outlook account. Error 0x8004210A is displayed in any one of the following formats on your PC:

The operation timed out waiting for a response from the receiving (POP) server 0x8004210a Task 'SMTP server name - Sending and Receiving reported error' (0x8004210A): 'The operation timed out waiting for a response from the receiving (POP) server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).'

Error Causes

Error 0x8004210A occurs due to several reasons. However, some of the most common reasons include:

• Wrong port number for the POP incoming server
• Your connection to the mail server is too slow
• Incoming and outgoing emails are being scanned and stopped by an antivirus installed on your system
• The Outlook send and receive job is being blocked by Firewall
• You are sending and receiving large series of emails or large email attachments
• Registry issues

No matter what the cause of this error is, to resume email communication via Outlook and to ensure your work productivity is not affected, it is recommended that you resolve this 0x8004210A error code on your PC immediately.

Further Information and Manual Repair

To fix error 0x8004210A, here are some of the most efficient and easy manual methods that you can try:

Method 1

If the cause of the error is related to the internet connection then here’s what you need to do. Try freeing up your internet connection by closing any other online activities in progress or downloads being carried on your system.

Method 2

Try to increase your server time-out periods. To do this, go to the Outlook File menu and choose account settings. Now double click on your email account and more settings. Now click advanced and increase your server timeout period to resolve.

Method 3

If you are trying to send or receive large and heavy emails on your Outlook account, the error 0x8004210A may pop up. This happens because when transferring heavy files the email account automatically locks until the task is complete, however, if it takes more time the next Send and Receive job starts while the first one is still not complete. In such an event, the email server then times out and shows you the error. Therefore to resolve, you will have to show patience. Simply wait for the large email to be sent or received before you start sending another email.

Method 4

If the antivirus installed on your system is the reason for the error pop up, then disable it for a while until the operation is complete. Then enable it once the task is performed successfully.

Method 5

Similarly, if the Firewall installed on your system is preventing Outlook from reaching your mail server, then simply disable the Firewall to resolve.

Error code 0Xc004F074 - What is it?

Did you previously use Windows 7 or 8 but decided to run with the latest Windows 0S, Windows 10? An early error message encountered was activation error code 0Xc004F074. Error code 0Xc004F074 is manifested when the user fails to activate Windows directly after the installation of Windows 10. This occurs if the previous operating system on your computer was Key Management Service (KMS) activated.

The KMT provides a more seamless operation when users are activating volume license editions of Microsoft Windows and Office. This process tends to be clear to end-users of the system.

Symptoms of error code 0Xc004F074 include:

• Windows is unable to reach your company’s activation service.
• The Key Management Service is unavailable.

Solution

Error Causes

Various factors might incite error code 0Xc004F074. A primary cause is a discrepancy or difference between the KMS client and the KMS host machine. The host computer could possibly be operating a Windows Server 2003 or Windows Server 2008, while the client runs on OS Windows 7 or Windows Server 2008 R2. To supplement, the computer’s time might be a contributing factor. The time on the host machine and client might show a difference (Usually the host time exceeds 4 hours).

Further Information and Manual Repair

To rectify error code 0Xc004F074, users are advised to try various methods. These methods include:

1. Method 1: Update Your KMS Host 9 (Windows Server 2003)

Are you running later versions of Windows Server? Use an update that fixes or installs KMS on your computer. The update is available on Microsoft’s website. Keep clearly in mind that the update is only for Windows Server 2013 Service Pack 1 and later versions of Windows Server 2003.

2. Method 2: Update Your KMS Host 9 (Windows Server 2008)

This step is similar to the aforementioned. However, it applies to Windows Vista and Windows Server 2008. This ensures the service is extended to Windows 7 and Windows Server 2008 R2.

3. Method 3: Update the Time

It was previously mentioned that the time reflected on the KMS host and client might cause error code 0Xc004F074 to manifest. A simple fix to adhere to is to always ensure that the time between both is updated. To Resync the time on the client, execute the following command.

w32tm /resync

4. Method 4: Uninstall the Existing KMS

For this method to be successfully deployed, you’ll need to have in your possession an activation key or KMSpico Key. As you cannot apply the new key with the existing one, remove or uninstall the initial key. To perform this step, open the command prompt. This should be done while the computer is in admin mode. Then, run the command

(slmgr.vbs /dlv)

It should be executed without the brackets and before you have removed the existing key.

After executing the command, you’ll encounter the description:

Windows(R) Operating System, VOLUME_KMS_WS12_R2 channel

Move along with the process by applying the slmgr.vbs /upk to uninstall the existing KMS key.

After the old key is uninstalled, you’re ready to apply the following:

slmgr.vbs /ipk <NewKMSProductKey>

To check if things are in place and complete the process, follow the steps below: PC Settings >Update and Security > Activation

5. Method 5: Download an Automated Tool

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

What Is Error 126?

Error 126 is a very commonly occurring error that is often the result of damaged system files of Windows. They usually occur during the installation of some Windows program or application. When Error 126 is generated, it terminates the installation process almost instantly. It is important to take corrective measures immediately to ensure that no such problems are encountered again in the future.

Solution

Error Causes

There are a variety of conditions that may trigger Error 126. These conditions are listed below as follows.

• Corruption of the service-related DLL file
• Missing or damage service-related DLL file
• Corrupt, damaged, or Misconfigured system files
• Improper hardware or application installations or uninstallations
• Existence of viruses, malware, adware, or spyware in the system
• Corrupt or incorrect registry entries in the system files

When any of the above-listed conditions occur, the corrupt system files will go to the improper links or missing information. Eventually, the problems with the files will keep the applications or programs from responding in the usual manner. Whatever are the reasons for error generation, it is of utmost importance that the error is removed to ensure smooth functioning of the system.

Further Information and Manual Repair

There are many different ways this error can be rectified. However, the two most effective solutions are listed below as follows.

• This solution is for the advanced user. Turn on the system and log on to it as the Administrator. Now click on the Start button. Now click on All programs -> Accessories -> System Tools. Here you will come across the option for System Restore. Click on it. A new window will appear. Select 'restore my computer to an earlier time' point. Now clock on Next. A list of restore points will now appear in front of you. Choose the latest restore point you come across from this list and click on ‘Next’. In the next window that opens, click on ‘Next’ again. This is the confirmation window. Once the restoration finishes, restart your computer.
• This solution is for novice users. Download an Error 126 repair utility program. Install it on your system. Now use it to scan your system for errors. Find out if there is an option to fix/repair error. When you come across it, click on it as soon as the scan is complete. Restart your computer. Your system is now free of Error 126.

As you know, DLL files in the Windows environment contain all the code needed by programs in order to properly function. And like with most other software, the functions in the DLL file have to be compatible with Windows especially if they are using any built-in service. So if you encounter an error that says, “DLL is either not designed to run on Windows or it contains an error”, when you try to launch a program, then this could be due to a compatibility issue. To fix this error, read on as this post will walk you through doing that. Based on the reports of users who encountered this error, the error pointed to a DLL file that was either designed to run on a different version of Windows. It is also possible that the DLL file itself is the problem. Here’s the complete error message:

“Bad Image – DLL file is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.”

According to security experts, the DLL files that are known to trigger this kind of error message are msvcr100.dll, msvcr110.dll, msvcp140.dll, lmirfsclientnp.dll, and so on. To fix this problem, you can try to update or reinstall the program that’s throwing the error to its latest version. You could also ask the vendor for the latest version of the DLL as well as run a System File Checker scan.

Option 1 – Try to update or reinstall the program to its latest version

The first thing you can do to fix the problem is to update or reinstall the program that’s throwing the error. It is possible that the version of DLL might be using a system call that is deprecated. So if you had updated your Windows 10 computer recently, you might want to check for an update of the software or you could also try to reinstall its latest version.

Option 2 – Try asking the vendor for the latest version of the DLL

The next thing you can do to fix the error is to ask for the latest version of DLL from the vendor. There are times when the software uses an open-source version of DLL so it is better if you ask the vendor if there is a DLL file that has to be updated. If there is, then you need to make sure to register the DLL once you have it.

Option 3 – Try to re-register the problematic DLL file

You can also try to re-register the DLL to resolve the problem. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 4 – Try to replace the DLL file from a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:/Windows/System32
  • x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 5 – Run System File Checker scan

If reinstalling the program didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys 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.

 Reboot your computer.

Option 6 – Troubleshoot the isDone.dll error in a Clean Boot State

You can also troubleshoot the “DLL is either not designed to run on Windows or it contains an error” in a Clean Boot state. It could be that there are some third-party applications in your computer that are preventing the application from getting installed 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, make sure that you’re signed in as administrator and then try to install the application again.

Option 7 – Try scanning your computer using Windows Defender

The DLL file might also be infected with malware or virus and to eliminate it which could explain why you’re getting the “DLL is either not designed to run on Windows or it contains an error”. Thus, 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.

0x00000050 - What is it?

0x00000050 is a type of stop error code. It is also known as a Blue Screen of Death error. It usually occurs when you try to start your PC or load a program. It can also occur while running a program. This error may also pop up when you restart your PC after installing Windows XP Service Pack (SP1) on your computer. Unlike some PC related errors, 0x00000050 error code occurs without any warning. The stop 0x00000050 error is displayed in a blue screen and interrupts you from carrying your desired activities on your PC smoothly. This error message is prompted in the following format:

Stop 0X00000050 (parameter1, 0, parameter3, parameter4) PAGE_FAULT_IN_NONPAGED_AREA”

Solution

Error Causes

Stop 0x00000050 error code may pop up on your Windows computer screen due to multiple causes. The most common causes for this error code include:

• Poor PC maintenance
• Registry issues- Bad registry keys, invalid entries, corrupt and damaged registry
• Incompatible DLL files
• Corruption of system files- Pool corruption in the Srvnet.sys file
• Spyware and viruses
• Overheating of PC components
• The conflict between Windows XP SP1 and the display adapter drivers that are currently installed on your PC.

It is advisable to resolve 0x00000050 error code on your PC right away. BSOD errors are fatal errors and can pose serious threats to your PC. If not fixed timely it can lead to system crash, failure and valuable data loss.

Further Information and Manual Repair

To prevent data loss and system failure, there are some effective methods to resolve Stop 0x00000050 error code on your PC.  To implement these solutions on your PC, you don’t need to be a technical whiz or a computer programmer.

Method One

If the error cause is the conflict between Windows XP SP1 and the display adapter drivers then here’s what you need to do to resolve it:

1. First start Windows in safe mode. To do this, restart your computer and press F8. On the Windows Advanced Options Menu, use the arrow keys to select Safe Mode.
2. Once you select it press enter. Now use the arrow keys to select the operating system, press enter to start your computer in safe mode.
3. Go to Start, click Run and then type ’msinfo32’ in the open box and press OK to continue. Then under the System Summary option, expand Components and then click Display to note the information that corresponds to the INF File Item. And then simply quit the utility.
4. After that, go to the start menu again and then the My Computer and Properties option.
5. Press the Hardware Tab and then click the Device Manager tab. Go to the ‘Display Adapters’ option and press the option ‘Uninstall. To confirm action press OK.
6. Once again, go to the start menu and run and then type the following commands as illustrated below and after each command press enter.

• ren %systemroot%infINF file name from Step 5.inf *inf.old
• ren %systemroot%infINF file name from Step 5.pnf *pnf.old

This procedure may look pretty lengthy but it is worth it. Once you insert the commands, close all open windows and then reboot your system. Now download the latest drivers for your display adapter and install them. This will hopefully resolve the 0x00000050 error code on your system.

Method Two

Sometimes 0x00000050 BSOD error may occur due to temporary issues like overheating PC components. In times like these, all you need to do to fix the issue is to switch off your computer and allow the components to cool down. Try starting your PC after a few hours.

Method Three

If the issue is triggered by malware, then it is advisable to download a powerful antivirus. Scan your entire PC to detect and remove viruses affecting your PC and generating BSOD errors on your system.

Method Four

However, if the error still persists after trying all the methods stated above, then this means the cause of the error is deep-rooted. It is related to the Windows registry. Registry stores all your system files and activities performed on your PC. It usually gets damaged and corrupt if it is not cleaned frequently. The registry loads with unnecessary and obsolete files like junk files, cookies, internet history, bad registry keys and invalid entries. These files if not removed, accumulate and damage the registry, DLL files, and system files too thereby generate BSoD errors like 0x00000050 error messages. You can clean and repair the registry manually but it requires a great deal of expertise. The ideal and easiest way to clean it is to download Restoro. This is highly functional and easy-to-use software. It is embedded with multiple powerful utilities including such as a registry cleaner, an antivirus and a system optimizer. The registry cleaning feature scans for all errors related to the registry. It removes obsolete files, invalid entries, restores damaged DLL and system files. The antivirus feature simultaneously detects and removes all kinds of malware. These include viruses, Trojans, spyware, and adware affecting your PC. While the system optimizer feature ensures that your PC functions at its optimum speed. It is a safe and powerful PC Fixer. It has a user-friendly interface and compatible with all Windows versions. Click here to download Restoro and Fix Error 0x00000050

D3dx9_32.dll Error - What is it?

D3dx9_32.dll is basically a type of dynamic link library used to load and run different programs on the PC. The D3dx9_32.dll error message pops on the screen when this file is unable to load successfully. The error message is displayed in either of the following formats on the computer screen:

"The file d3dx9_32.dll is missing" "D3DX9_32.DLL is missing. Replace D3DX9_32.DLL and try again." "File d3dx9_32.dll not found" "D3dx9_32.dll not found. Reinstalling might help fix this." "Missing component d3dx9_32.dll"

This error usually pops while using gaming software. The D3dx9_32.dll error is displayed after a game is loaded or before the game-play begins. However, it may also appear in software that uses advanced graphic features.

Solution

Error Causes

D3dx9_32.dll error may occur due to multiple causes. These include:

• The problem is related to Microsoft DirectX software. This software includes the D3dx9_32.dll file in its software collection.
• Incompatible Video Card Drivers
• Improper game installation
• DLL File Corruption
• Registry issues
• Viral infection

Further Information and Manual Repair

To avoid inconvenience, it is advisable to fix the error right away. To resolve it you don’t need to be a technical whiz or hire a technician. Luckily, the D3dx9_32.dll file error is quite easy to fix. Here are some of the best and effective DIY methods that you can try to remove the error:

Method 1 - Install the Latest Version of DirectX

Since D3dx9_32.dll error is related to DirectX software, it is advisable to make sure that you have the latest version of this software installed on your PC. To install the updated version, simply go to Microsoft’s official website, download the software from there and install it on your PC. To activate changes, restart your computer.

Method 2 - Uninstall and then Re-install Gaming Application

If the error still persists, then the reason for it could be the gaming application. Sometimes D3dx9_32.dll error may also occur due to poor program installation. Therefore, in this case it is recommended that you first uninstall the program by going to the Add/Remove program option. And once the program is uninstalled, try re-installing it on your PC. Hopefully, it will remove the error.

Method 3 - Restore the Damaged/Corrupt D3dx9_32.dll File

The error may also pop due to the damaged or corrupt D3dx9_32.dll file. This indicated registry issues. When the registry becomes overloaded with unnecessary and obsolete files, there is not enough space for other files to store. Due to the poor registry maintenance, the system and dll files are often damaged. To restore the damaged D3dx9_32.dll file, you need to clean the registry first. You can do this manually, but that will be quite time-consuming and slightly technical. Therefore, download a registry cleaner. A registry cleaner scans all registry-related errors and removes them right away. It cleans the registry and restores the damaged dll files.

Method 4 - Scan for Viruses

If the D3dx9_32.dll error is triggered by viruses, then it is advisable to scan your PC with an antivirus. It will scan and removes all viruses from your system. Whether D3dx9_32.dll error is related to registry issues or viral infection, download Restoro. It is a cutting-edge, advanced, and multi-functional PC Fixer. A one-stop solution for all PC-related issues. It is deployed with a powerful registry cleaner, an antivirus, a system optimizer and several other scanners. The registry cleaner detects and removes all registry errors and repairs damaged Dll files including D3dx9_32.dll file and simultaneously the antivirus utility scans your entire PC for all types of malicious software infecting your system including spyware, Trojans, adware and malware. The system optimizer feature ensures your PC works at its optimal level. Restoro PC Fixer is safe and efficient. It has a user-friendly interface which makes it quite easy for all levels of users to operate. In just a few simple clicks, errors are resolved. In addition to this, you can download it on all Windows PC. It is compatible with all Windows versions. Click here to download Restoro and resolve D3dx9_32.dll error code on your PC today.

A lot of programs in Windows utilize the helper processes to ensure that they can get the job done as early as possible. And one of the programs that use these processes is Microsoft Edge. This built-in browser uses a process called the Edge Content process. The moment you start your computer, these system processes are loaded which makes the Edge browser load faster. To be specific, these are the three processes that are related to Microsoft Edge:

• MicrosoftEdge.exe
• MicrosoftEdgeCP.exe
• MicrosoftEdgeSH.exe

The process that ends with the “CP.exe” is the content process in Edge. However, when this process stopped working, this can affect the Edge browser. In such cases, when you check the Reliability Monitor, you will see that the state of the “Microsoft Edge Content Process” is “Stopped working” which keeps on appearing. To resolve this issue, you can try to clear the browsing data of Microsoft Edge or repair or reset it. You can also try re-registering Edge via Windows PowerShell as well as check your security programs that might be causing interference with the process.

Option 1 – Clear the browsing data of Microsoft Edge

• Open Microsoft Edge.
• Then click on the three horizontal dots to open the menu.
• From there, click on Settings. And under Settings, click the “Choose what to clear” button under the Clear browsing data section.
• Next, check all the checkboxes and then click the Clear button to clear the browsing data in the Edge browser.
• Restart Edge.

Option 2 – Try to reset, repair or reinstall Edge via Settings

You can reset, repair or reinstall the Edge browser through Settings. If none of it helped, you can try the following:

• Open File Explorer and then go to this path – C:/Users/YourUsername/AppData/Local/Packages

Note: Before you type in the path in the Address bar, make sure that you put your user account name in place with the “YourUsername”.

• Tap Enter to proceed.
• Next, look for the folder named “MicrosoftEdge_8wekyb3d8bbwe” then right-click on it.
• Click on Properties and uncheck the option “Read-only” under the General tab in the Properties window.
• Click on Apply and then OK to save the changes made.
• After that, look for the MicrosoftEdge_8wekyb3d8bbwe folder again and delete it. And if a prompt stating “Folder Access Denied” appears on your screen, just click on the Continue button to proceed – doing so will delete most of the content inside the folder except for the folder named “AC”.
• Restart your computer

Option 3 – Re-register Edge via Windows PowerShell

• In the Start Menu, search “Windows PowerShell”.
• Right-click on Windows PowerShell from the search results and select the “Run as administrator” option.
• Type in this command in the PowerShell windows and tap Enter – Cd C:/Users/YourUsername
• After that, type in this command and tap Enter – Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml" -Verbose}
• Restart your PC.

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml” -Verbose}

Option 4 – Try to check your security program

It is possible that a security program installed in your computer is the one that’s causing the problem which is why you have to check it. According to security experts, there are some security programs that could be detecting the Edge’s content process as suspicious, blocking or terminating it as a result. Thus, you need to modify your security program’s settings to fix the problem.

Code 21 - What is it?

Code 21 is a Device Manager error code that appears when you try to use a hardware device attached to your computer and the Windows prohibits you from using it.

This is due to the Windows experiences problems loading the device driver. This error message is displayed in the following format:

“Windows is removing this device. (Code 21)”

Solution

Error Causes

Error code 21 means that Windows is in the device removal process and the device has not been completely removed. It occurs when you set a device to be removed and then select the same device to run on your system.

Upon your instructions, Windows start to remove that device and when you on the other hand try to use/access the same device that you selected for removal, it kicks up Code 21.

Further Information and Manual Repair

If you are experiencing error code 21 on your PC, it is advisable to resolve it immediately.

Though this error will not damage your system, but will significantly lower the performance of your PC which is definitely something you don’t want especially if you work on your computer daily and use it to perform important time-sensitive errands.

To repair and resolve, try the methods given below:

Method 1 - Wait for a Few Seconds and Then Press F5

This is one of the best and easiest ways to resolve code 15 on your system. Wait for a few seconds, and then press the F5 key. This will update the Device Manager view and the error will most probably go away.

Method 2 - Restart Your PC

Sometimes error codes may pop up due to temporary glitches. To resolve such errors, a simple reboot of your PC is enough. Shut down Windows and then restart your system.

This is most likely to resolve Code 21. However, if the error still persists then this means the underlying problem for code 21 is deeper than you think. Try method 3 to resolve.

Method 3 - Install DriverFIX

As mentioned earlier, the error code 21 may occur if you have selected a device to remove and then you try to reuse it.

To resolve, you may have to install the device again and the driver for that the reinstalled device. To reinstall the driver without any hassle, simply download DriverFIX.

It is a smart, user-friendly, and intuitive software program designed to resolve driver problems. The program is embedded with intelligent device identification technology which:

• Automatically detects all the appropriate system drivers
• Matches them with the latest available versions
• And then updates drivers according to their compatible versions on a regular basis

Furthermore, it enables accurate installation and ensures that your system is running at its optimal speed.

Other features that this program boasts are full backup and restoration, safe USB management, and ejection.

If nothing works, you can try the full backup and restoration feature and restore your PC to its previous state when it was functioning properly before the error occurred.

DriverFIX creates a backup of all your files and data hedging keeps you from disasters like data loss. It restores the system to the time when it was working properly.

Click here to download DriverFIX on your system and resolve error code 21 today.