How to Fix Error Code 0x80072EE2 in Windows 10

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 in Loading DLL - What is it?

This is a Dynamic Link Library (DLL) error. It results when a program calls upon a DLL file to perform a certain task and the file fails to load as it is damaged. In a nutshell, DLL is a collection of small programs. DLL is called upon by the executable program (EXE) that is running. The DLL file allows the executable program to run on the system. For example this error may occur when you try to run wizards in Microsoft Office Access such as the Import Wizard, the Report Wizard or the Control Wizard. This error is usually displayed as:

“Error in loading dll” “Object library not registered”

Solution

Error Causes

The error in loading DLL occurs due to numerous reasons. Some of the most common causes include:

• The DLL or the referenced DLL is not in a directory specified in the path.
• DLL File is damaged due to hard disk errors and registry corruption
• Registry key may not exist
• Malware errors add malicious codes to the application
• Spyware and adware infections

When you come across error in loading DLL, it is advisable to fix it right away as this error can pose serious threats and lead to your PC malfunctioning. It can corrupt programs and put you at risk of data security and privacy threats.

Further Information and Manual Repair

To resolve this error in loading DLL files, you don’t always have to hire a technician even if you don’t have technical knowledge. This error is quite easy to repair. Here are two ways to resolve error in loading DLL without any professional assistance:

Solution 1: Reinstall the Program

Reinstalling the program can help you resolve this issue. However, when doing this you will first have to uninstall the program and also remove the DLL files from the registry to ensure the update is carried successfully. In addition to this, you will also have to uninstall some programs that share DLL files with the program that you are removing from your system to reinstall it again. Windows will prompt the DLL shared message if it is being shared by other software on your system. Though this is a method used to resolve errors in loading DLL this can be slightly tricky and confusing for many.

Solution 2: Repair the Registry and Remove Malware

This is the best, easiest and most efficient way to repair error in loading DLL files. Did you know 94% of the PC-related errors are triggered by registry corruption and malware infection? To repair the registry and remove malware from your system, you don’t have to download a separate registry cleaner and an anti-virus. Simply download Restoro. Restoro is a cutting-edge and multi-functional repair tool integrated with powerful utilities like a registry cleaner, system optimizer, and an anti-virus. By running Restoro on your computer you can resolve all the underlying causes for error in loading DLL files in seconds. Whether the error results from registry corruption or viral infection, Restoro is the only tool you need to run to repair. It is a safe, efficient and a super functional tool. It has a neat layout, easy navigation, and a user-friendly interface embedded with advanced technology and automated algorithms that scan your entire PC and repair all kinds of PC issues right away.  It can be easily operated by even novice users.

Restoro features

The registry cleaner feature repairs DLL errors and corrupt registry. It removes all the unnecessary and obsolete files that have overloaded and damaged the hard disk. It scans and wipes out such files clearing up the disk space. It fixes mis-configured registry keys and settings thus resolving errors in loading DLL files. If your system is infected by malware it may create Dll.exe malicious files on your system. If these are viruses, they can damage your system. Malicious software like Trojan and spyware are detected and removed with the help of the privacy error detector module integrated into Restoro. Other features that are worth mentioning are its backup feature and outstanding Windows compatibility. With Restoro users can create backup files for data recovery in the event of data loss during repair. Also, it is compatible with all Windows versions. To resolve error in loading DLL files on your system you just have to perform 3 simple steps:

1. Click here to download Restoro.
2. Run it on your system to scan for errors in loading DLL files
3. Click repair to fix the issues.

Many users would probably agree that the Windows Media Player, in most cases, is a lot better than the Groove. Although it is understandable why the Groove Music app was created, it may be time for Microsoft to bring its focus back on Windows Media Player. Even more, so that some users are experiencing an issue where they were not able to play their playlist in the Windows Media Player on their Windows 10 PCs. One particular user claimed that when he removed his music from the C drive and transferred them to the C drive for some reason he didn’t state. Right after he did that, any attempts to play songs in the Windows Media Player just don’t seem to work. Transferring music to a different location shouldn’t cause any issue but for some unknown reason, it did. According to security experts, the reason why the Windows Media Player didn’t play the playlist is that it still believes that the songs are still located in the C drive when they’re really not. So the question here is, how can you get the Windows Media Player to recognize the exact and correct location of the songs? Worry not, for this post will show you how exactly you can do that. Carefully follow each one of the instructions given below to fix the Windows Media Player issue.

Option 1 – Try running the WMP Troubleshooters

In case there are any issues with the Windows Media Player, you can always count on the WMP Troubleshooters to fix the problem for you. These built-in troubleshooters, namely, Windows Media Player Library and Windows Media Player DVD Troubleshooters can help you fix the problem, so run them both and see if you can now play those songs or not.

Option 2 – Try rebuilding the Windows Media Player Database

If the first option didn’t work for you, you might have to rebuild the Windows Media Player database. You can do this by following the steps below.

• Tap the Win + R keys at the same time to open the Run dialog box.
• After that, copy and paste this command in the field: %userprofile%Local SettingsApplication DataMicrosoftMedia Player
• Once you’ve pasted the command, hit Enter then you will see a new File Explorer which is the folder for the Media Player. You will have to delete every item in this folder, except for the folders. Meaning to say, you must only delete the individual contents inside but not the folders.
• Now launch the Windows Media Player again and watch as it rebuilds the music library automatically.

‘R6025 pure virtual function call’ is a runtime error that occurs suddenly on the screen and disrupts the program being run prior to it. This error display indicates that the program has been corrupted. R6025 runtime error usually occurs with the Visual C++ framework.

Solution

Error Causes

This error occurs when the C++ program crashes which is usually because of the malfunctioning or missing of the device driver or incomplete device driver files. It happens because your application indirectly calls a pure virtual member function in a context where a call to the function is invalid. Most of the time, the compiler detects it and reports it as an error when building the application. R6025 error is usually detected at run time.

Further Information and Manual Repair

To fix the R6025 pure virtual function call error, you need to find the call to the pure virtual function. After you find the call, you need to rewrite the code so that it is not called again. There are 2 ways to do this:

Alternative 1

One way to fix the R6025 pure virtual function call is to replace the function with an implementation that calls the Windows API function DebugBreak. The DebugBreak causes a hard-coded breakpoint. Once the code stops running at this breakpoint, it is easy for you to view the call stack. By viewing the call stack you can identify the place where the function was actually called.

Alternative 2

Another quick way to find a call to a pure virtual function to fix the R6025 error is to set a breakpoint on the _purecall function that is usually found in PureVirt.c. By breaking this function you can trace the problem occurring and rewrite the call to ensure the error does not occur and the program you are trying to develop on the Visual C++ framework is easily developed. If R6025 Error is related to Windows Registry Problem Then here’s how you can fix the problem: To fix the runtime error R6025, run registry cleaner software to scan and fix all errors.  This alternative is suitable if the R6025 error is related to the Windows registry problem and where the error has occurred due to corrupted or malicious registry entries. You can download the registry cleaner repair tool for free. Run it to scan errors and then click the fix error button to repair the problem immediately.

What is Error Code 1309?

Error code 1309 is an error code that occurs when installing either Microsoft Office 2003 or Microsoft Office Project 2003. This error code may hamper your ability to run and use applications associated with Microsoft Office. To ensure installation is successful, it is first advisable to fix this error code. Error 1309 is displayed in any one of the two formats illustrated below. When installing Microsoft Office Project 2003, the error message may pop up as:

Error 1309. Error reading from file:    pathfilename.cab. Verify that the file exists and that you can access it.

When installing Microsoft Office 2003, the error message may appear in the following format: Fatal Error During Installation

Solution

Error Causes

Error code 1309 message may appear during Microsoft Office installation due to several reasons. These include:

• Problems in the Oclncore.opc file. Project 2003 uses this version of the file for program installation.
• Lack of adequate use permission
• The requested file was not found
• Setup registry entries are modified in an unacceptable manner

To avoid inconvenience and access Microsoft Office 2003 or Microsoft Office Project 2003, it is recommended to fix the error immediately.

Further Information and Manual Repair

To resolve this error you don’t need to be a technical whiz. Here are some of the best, easiest, and proven do-it-yourself methods to resolve error 1309 on your computer screen instantly.

Method 1 - Change CacheLevel Settings

If the problem is related to Oclncore.opc file then try changing CacheLevel settings. Follow these steps to work around this method.

1. First, locate the PRJPRO*.XML file in the FILESSETUP folder of the Project 2003 installation source and then open this file in the Notepad.
2. Also, make sure that you do not open the file as read-only and make sure that a checkmark is not displayed next to Word Wrap on the Format menu.
3. The next step is to search the file for the following text string: OCLNCORE.OPC_1033.
4. Now on the line where this string is located, change the CacheLevel=’1’ setting to the following CacheLevel=’3’ save the file back to the original location, and then quit Notepad.

After the changes are activated, try installing the software again on your system. If it installs successfully, then this means error 1309 is resolved. If the error still persists then try other given methods.

Method 2 - Configure security settings to get full permission

When the cause of error 1309 on your PC is related to lack of adequate permission issues, then configure security settings to resolve. To do this, simply locate the folder on your installation drive. Then right-click the folder and click Properties. On the Security tab, click edit and now make sure your user name is added to the list. Grant required security permissions and then click OK to save changes. After this, try installing Microsoft Office 2003 again on your system.

Method 3 - Copy the requested file from another source

If the error 1309 pops up because the requested file was not found, then try this method. Simply copy the file specified in the error to the destination directory. For example, if the error shows data1.cab was not found, then copy this file from another source and paste it into the directory specified in the error description.

Method 4- Remove bad registry entries

Bad registry entries are responsible for registry setup modification. If this is the reason for error code 1309, then download Restoro. This is a user-friendly PC Repair Tool embedded with a powerful registry cleaner. It scans and removes all bad and invalid entries accumulated in the registry. It cleans and repairs the registry resuming it back to its normal function. Click here to download Restoro and repair error 1309 today.

Error Code 0x80d02002? - What Is It?

Error Code 0x80d02002 is one of the common errors encountered by Windows users upgrading to Windows 10 or installing new Windows updates. This error results in program lock-ups, system crashes, and freezes, or slow PC performance. It can also cause possible loss of private data on your device.

Some of the common error messages involving Error Code 0x80d02002 include:

• Something went wrong, Please try again later. Windows update error dt_000 – 0x80d02002
• Error(s) found: Code 0x80d02002 Windows update encountered an unknown error. Windows update ran into a problem.
• Windows Update Cannot Check For Updates – 0x80d02002
• 0x80d02002 – Windows could not search for new updates. An error occurred while checking for new updates for your computer. Some updates were not installed.
• There were some problems installing updates, but we’ll try again later If you keep seeing this and want to search the web or contact support for information, this may help – 0x80d02002

While upgrading to Windows 10, depending on the state of your computer, you might encounter other error messages, including error code 0xc000021a. 

Solution

Error Causes

Error Code 0x80d02002 normally occurs when a user updates their system, upgrades to Windows 10 from Windows 7 or Windows 8/8.1, or installs new Windows updates. There are several reasons why this error happens which includes:

• Internet connection problems
• Blocked system ports
• Conflict on system level

Further Information and Manual Repair

In trying to fix Error Code 0x80d02002, you can employ manual repair methods to effectively and efficiently solve the issue. However, keep in mind that one tiny error made in using the command prompt can result in data loss or put your computer in a no-boot situation. In such cases, you can seek help from a Windows professional or consider using an automated tool whenever necessary.

You can try doing the following manual repair methods in an attempt to fix Error Code 0x80d02002:

Method One: Reset Windows Update Components

In trying to fix Error Code 0x80d02002, you may try resetting manually and check the Windows update components by doing the following steps:

1. Right-click on the Start button then select Command Prompt (Admin) from the list to open a Command Prompt window.
2. Once the Command Prompt window appears, type or copy and paste the following commands all at once then hit Enter:

net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:WindowsSoftwareDistribution SoftwareDistribution.old ren C:WindowsSystem32catroot2 catroot2.old net start wuauserv net start cryptSvc net start bits net start msiserver pause

3. Exit the Command Prompt then check if the issue is resolved.

Method Two: Check If The Region Is Correct

1. On the Start screen, type Region. Afterward, click on Settings then hit
2. Under the Format tab, choose English (United Kingdom).
3. Select Language Preferences then click on Add a language. Afterward, add “your language.”
4. After you’ve added your preferred language, choose it then click on Move Up to make it the first language. Close now the Language window.
5. On the Region window, select Additional Settings and see if the values are the same.
6. Select the Location tab then change the Home Location to “your country,” then hit

Method Three: Perform an SFC Scan

Check if there are system files that need to be repaired by running an SFC Scan. Follow the steps below:

1. Type CMD in the search bar then right-clicks on it. Select Run as Administrator. This will open a Command Prompt window in elevated mode.
2. In the next window, select
3. Once the Command Prompt window appears, type the command: sfc /scannow
4. Leave the Command Prompt window open and wait for the process to complete. This might take a while depending on how fast or slow your device is.
5. When everything’s fine, the message saying “Windows Resource Protection did not find any integrity violations” will appear.

 Method Four: Disable Skype or Antivirus

There are times when Skype or your installed antivirus can conflict in updating your system. You can disable first your antivirus or Skype as you update your system and enable them once again when you successfully update your system.

Method Five: Download A Powerful Automated Tool 

Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!

There are instances when you have to connect to another Windows 10 PC via remote connection from another Windows 10 PC. However, when you encountered an error saying, “Your password may have expired or the remote pc might not accept blank passwords” while doing so then read on as this post will walk you through how you can fix it. Here is the full content of the error message:

“Your password may have expired, or the remote PC might not accept blank passwords. Try connecting again. If this keeps happening, ask your admin or tech support for help.”

It is unknown what the exact cause of the error message is as it could involve several factors. Even so, there are still various potential fixes you can try to fix this kind of error. You can try to check if your password has expired or troubleshoot any issues with the network. You could also use a remote desktop application or configure the settings of firewall or restart the remote desktop service. For more details, refer to each one of the given options below. But before you proceed, make sure that you have someone to help assist you on the other side to help you troubleshoot the issue.

Option 1 – Try to check if the password has expired

The first thing you can do to fix the problem is to check if the password has expired as it could be the reason why you’re experiencing this problem. You have to make sure that you are using a user account that is on the remote computer and then check if the user account password has not expired yet. And if your PC is not within your access, then you can just ask someone to verify the password for you.

Option 2 – Try to troubleshoot network issues

To troubleshoot network-related issues that might be the one that triggers the error, you need to run the Network Troubleshooter. To get started, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 3 – Try to use a remote desktop software

A number of users reported that the issue occurred when they used the universal app for Remote Desktop and they were able to fix it by switching to the Remote Desktop application. Thus, you can try to switch to the remote desktop software and see if it fixes the problem or not.

Option 4 – Try to configure Firewall settings

You might also want to configure the settings of the Firewall as it could also help in fixing the problem. It is possible that the firewall is blocking the incoming connection on the remote computer. To check if whether the firewall is the culprit or not, follow the steps below.

• Go to Windows Security and then go to Firewall and network application.
• Next, click on the Advanced Settings link. This will open the classic Windows Defender Firewall and Advanced Security application.
• From there, look for the rule named “Remote Desktop – User Mode (TCP-In)” under inbound rules and check if it has been disabled or not.
• If the rule is disabled, you have to enable it.
• Once done, check if the error is now fixed or not.

Option 5 – Try to restart the Remote Desktop service

If none of the four given options given above worked, you might want to restart the Remote Desktop service as it can help you in fixing the problem. To do so, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the Remote Desktop Service and right-click on it, and then click on the Restart option.
• Once done, check it was able to fix the “Your password may have expired or the remote pc might not accept blank passwords” error or not.

Security on your PC and on your accounts is the important thing. Security on your phone device is also very very important. That is why we are bringing you a list of 8 applications that are marked by the cybersecurity team as ones that could be used to steal data from you. If you have by any chance any of these applications installed, uninstall them immediately.

List is as follows:

• Cake VPN (com.lazycoder.cakevpns)
• Pacific VPN (com.protectvpn.freeapp)
• eVPN (com.abcd.evpnfree)
• BeatPlayer (com.crrl.beatplayers)
• QR/Barcode Scanner MAX (com.bezrukd.qrcodebarcode)
• Music Player (com.revosleap.samplemusicplayers)
• tooltipnatorlibrary (com.mistergrizzlys.docscanpro)
• QRecorder (com.record.callvoicerecorder)

If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

As you know, storage devices are an important part of the computer system for porting, saving, and extracting data files. And for you to differentiate between storage devices on your computer system, each one of the storage devices is labeled with a unique number referred to as Disk Signature for identification. The unique disk identifier is stored as a part of the MBR or Master Boot Record. Disk signature is used by operating systems in order to identify and set apart different data storage devices and hard disk drives in the computer for data access. These days, Disk cloning has become a regular practice in upgrading to larger hard disk drives. Drives are cloned in order to produce a similar copy to use both the original drive and cloned copy together. Moreover, lots of virtualization tools are being used to virtualize the physical hard disk drives to create virtual hard disk drives and several virtual machine clones that are created with the existing virtual hard disk drives. And since these are identical copies, chances these copies may have identical disk signatures. As a result, when you use both disks that have identical signatures at the same time you run into the Disk Signature Collision problem. This kind of problem does not often occur as the Windows system does not really allow two disks to function simultaneously when they have the same disk signature. When you encounter a Disk Collision problem in your Windows 10 computer, you may see the following error messages:

• The boot selection failed because a required device is inaccessible
• The disk is offline because it has a signature collision
• This disk is offline because it has a signature collision with another disk that is online

You can fix the disk collision problem by changing the disk signature which you can achieve using the command line utility diskpart in Windows PowerShell or Command Prompt or using Windows Disk Management utility. To fix the disk collision problem, you can make use of the command-line utility called diskpart in Windows PowerShell or Command Prompt to view and change the signature, or can make use of Master Boot record in the Windows Registry. You can also make use of Windows Disk Management Utility to change the signature. Simply follow the given options below to change the disk signature either way.

Option 1 – Change Disk Signature via Diskpart

• Type “command prompt” in the Windows Search bar and then right-click on the related search result and select the “Run as administrator” option.
• After that, type the “diskpart” command and hit Enter to open Diskpart.
• Next, type the “list disk” command to display all the disks available in the system.
• Next, take note of the problematic disk number with the status Offline from the list and then type the “Select disk x” command where x is the offline disk to select the offline disk. For instance, if you type “select disk 1”, it will display the “Disk 1 is now the selected disk” message.
• Now type the “Uniqueid disk” command to display the disk signature and to change the disk’s signature and set the disk online, type the “unique disk ID= (New signature)” where (New signature) is the new ID in hexadecimal. For instance, you can set the new id as “unique disk ID= 1456ACBD”.

Note: If you have given the wrong format ID, the command prompt will display the following error:

“The specified identifier is not in the correct format. Type the identifier in the correct format: in hexadecimal form for an MBR disk or as a GUID for a GPT disk.”

• After you’re done, the disk will be online, and then restart your computer.

Option 2 – Change Disk Signature via Disk Management Utility

• Tap the Win + R keys to open the Run dialog box and then type “diskmgmt.msc” and hit Enter or click OK to open Disk Management.
• Next, right-click on the disk that is marked as Missing or Offline.
• After that, select the Online command from the drop-down menu.
• Then from the selecting option Online, Windows will generate a new disk signature.

RAM drive is basically a hard drive made of your RAM memory. Altho this kind of drive can not and is not available to save any data when the computer is shut down its advantage is lightning fast speed since the application is installed in RAM itself, it is loading from there and executing from there. Creating this kind of drive which will use your RAM memory, well part of it can not be done natively in Windows, you will need some kind of application for this task. Luckily there is a free open source application for this kind of task. ImDisk, you can download the application here. ImDisk Toolkit is an application for managing virtual drives. It also includes a utility that allows the creation of RAM drives. Download the application and install it, make sure that you select all components on the installation selection screen. After installation is finished double click on icon labeled RamDisk Configuration. Once the application is running adjust the disk size in the box at the top of the window for your RAM drive. Click “OK” at the bottom of the window. This will create your RAM drive, which is just a virtual disk that’s assigned to your computer’s RAM. The process happens transparently, so there’s nothing you need to do. If you get a warning about shutdown settings, click on the “Shutdown Settings” button. Then unlock the settings pane with your administrator password. Finally, uncheck the checkbox next to “Turn on fast startup (recommended)” and click “Save Changes” at the bottom of the window. Your RAM drive is now ready for use. Fast Startup speeds up the process of turning on your computer by saving a system state between completely off and hibernation to your hard drive. This happens when the computer writes the contents of your RAM to a stable hard drive. As you may guess, this could mess with your RAM drive’s ability to preserve and track its data. With Fast Startup off, boots may take slightly longer, but it’s doubtful that you’ll notice much. Disabling a fast startup will satisfy the warning window, but let’s consider why. This will also allow ImDisk to save your RAM drive’s data to an image file when you shut down your computer. If you don’t, the contents of your RAM drive will be erased completely every time, with no saved image storage. It would also disable the RAM drive’s ability to load the previous content. Basically, the drive would act much more like RAM and much less like a disk. Depending on your use case, that may be disappointing or unusable. You can access and use it just like any normal hard drive. It shows up in Windows’s file explorer just like any other drive. However, a Ram drive is exponentially faster than traditional types of storage. And we mean exponentially. Whereas an SSD might offer 300 to 500 MB when reading from the disk, a RAM drive can offer more than 5000 MB, even on mediocre memory sticks.