Logo

Photo viewer on clean Windows 10 instalation

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.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

Coller Master HAF 700 evo

The New and upcoming HAF 700 Evo from Coller master is a beast of a case, but so is its price. The case itself is still not released but as sources say it will be soon, well at least we hope so. The price will be around $500 which is a little on the expensive side of things but the features it is bringing are very impressive.

cooler mster haf 700 evo

HAF 700 EVO Size and its advantages

HAF stands for High Airflow and with this case, you are going to get it but first let us talk about other characteristics of the case. Firstly case is ATX full tower, pretty big going 24.64 x 11.45. x 26.22 inches in size but like all full tower cases it can hold all motherboard types including Mini-ITX, Micro-ATX, ATX, E-ATX. The large case size also lets you place a pretty big GPU, going to 19.29 inches (490 mm) in its length covering currently all available Graphic cards on market.

Being a very big computer case is not just placing motherboard and big GPU, there are other great advantages of it, firstly that you can go wild with your CPU cooler, going all the way to 6.5 inches in cooler height will satisfy all users and having 12x 2.5 or 3.5-inch internal bays will. And if even that is not enough you have 8 expansion slots available.

Inside HAF 700 EVO

haf 700 evo inside

Inside the casing you will also find 2 front fans with 200mm diameter, 2 rear fans sized 120mm, and 1 bottom fan of 120mm. You can also manually mount standard 120mm fans on top of the case for maximum airflow.

Front panel and outsides

The front side is filled with 4x USB 3.2 Gen 1 Type-A (5 Gbps), 1X USB Type-C (up to 10Gbps), 3.5mm both headphone and audio jack along with a reset switch. Also, the circle in the very front is a hi-resolution LCD customizable display, you know, just to add more flavor and personal touch to the case. Fron is also filled with glass panels emitting RGB light.

Of course, you must also have a Tempered Glass Side Panel and well weight of 53.57 pounds (24.3 kg), yup you read that correctly, beside its hefty price tag this cooler master beast also is pretty heavy. Granted all of the weight comes from the glass front panel it is still a little hard on moving and taking out of the box.

This is also the case where you will not need a single screwdriver, everything is made to be assembled with your hands alone pushing easy assembly into the front row.

Conclusion

So in the end what are my thoughts about this expensive and heavy PC case? Would I recommend it? The answer to that question could depend really on your budget, let us be really honest here if you can afford it, YES, wholeheartedly I would recommend the case, it is great, it feels great, it looks great and the airflow is amazing. However, if you are tight on a budget, there are other great cases with excellent airflow and you might want to skip this one.

Read More
How to run old applications in Windows 10
Having the latest applications is often preferred for most users but sometimes we have some old applications which have not been updated or simply we just want to run oldie on our computer because it does everything we need and we do not want to upgrade in order to save some money. The issue is presented sometimes when we try to run an old application in Windows 10 and some components are missing in Windows itself or the application is simply coded in a way to work on older Windows versions. If by any chance you have this issue then this guide is for you since we are going to show you how to run old applications in Windows 10. This guide is made in a way to takes into account that the application itself is completely installed on your Windows 10 machine if you can not even install the application you will need to search solution for that particular application since that can not really be generalized and pinpointed issue, every application is different.

Running old applications using the compatibility option

All of that being said, let's start that old app you have. First thing is to locate an executable file or shortcut of the desired application. Once it is located, right-click on it to bring up the menu, and all the way to the bottom you will find properties. Left-click on properties. file properties drop down menuThe application settings screen will open, in upper tabs locate Compatibility and left-click on it. file properties compatibility tab markedAfter the click, you will find yourself in application compatibility settings. File properties compatibility optionsIn this window, you will face different options to run the chosen application in various modes in order to make it run. How settings are self-explanatory and different applications will need different settings sadly we can not cover them all but your safest bet is to run them in an environment where they have worked. For example, if the application was working fine in Windows XP and required administrator privileges, check Run this program as an administrator and Run this program in compatibility mode for Windows XP.
Read More
How to Fix Windows 10 Error 0x8007000d

Error Code 0x8007000d - What is it?

Error Code 0x8007000d is a common error code that can be found on the Windows 10 Operating system, although it can also appear in previous versions of the operating system, as well.

Common symptoms include:

  • Inability to download new updates.
  • Inability to run the Update tool through to completion.

There are four basic ways to try to resolve Error Code 0x8007000d on your Windows machine. Three of these are pretty simple for even the most basic users, while the final method requires some familiarity with running commands in the Command Prompt. If you don’t feel that you have the skill or confidence to complete the steps listed below, it is generally recommended that you get in touch with a qualified computer repair technician that can assist you in error resolution.

Error Causes

The main cause for the appearance of Error Code 0x8007000d on a Windows machine is that one of the files that the Update tool uses to run one or more updates cannot be found or has experienced damage. Fortunately, there are a few things that you can try on your machine that can be used to attempt to resolve the issues at hand.

Further Information and Manual Repair

Three primary methods exist for the resolution of Error Code 0x8007000d on a Windows machine. As mentioned above, two of these methods can usually be accomplished by basic users, while the third requires some degree of familiarity with the tools associated with the Command Prompt. If you don’t feel that you have the knowledge or skill necessary to follow these steps, contact a computer repair technician to aid you.

Here are the best ways to try to resolve Error Code 0x8007000d on your device:

Method One:  Use the Troubleshooting Tool from Windows Update

From the Windows Update tool, you can attempt to run a scan using the Windows Update Troubleshooter, which can try to identify the specific issue that is occurring and to fix it automatically.

Not only will this tool often fix the problem at hand, but it can also help you to avoid other errors that you may have encountered later on in the Update process. This tool should always be your starting point when you encounter an error as you attempt to download or install updates for your Windows machine.

After the tool has been run, restart your computer to apply any changes and then reopen the Update tool to reattempt installation.

Method Two:  Reset Your Computer

In some cases, the missing or corrupted files may be extensive enough that you need to restore your computer to an earlier point. If you create regular backups of your information or have a past version of the software that you can install, this can help you to resolve the issue. Otherwise, you may need to restore your device to its factory settings to resolve the error.

Always make sure to backup your important files and information before you perform a reset of your device, in order to ensure that you are able to return the computer to its original state when you have finished.

Method Three:  Use Command Line Tools to Resolve the Issue

One of the ways that you can try to resolve this particular error code is the use a DISM tool. This is accessed through the Command Prompt. In order to use this method, follow the steps below:

  • Step One: Open up the search bar in the Start Menu and type in the words “Command Prompt,” selecting it and choosing to run it as an administrator.
  • Step Two: Enter each of the commands below, hitting the “Enter” key when you finish each one:
    • exe /Online /Cleanup-image /Scanhealth
    • exe /Online /Clean-upimage /Restorehealth
    • Exit
  • Step Three: Attempt to run the Update program again. In some cases, you may want to restart your computer before you attempt to run the Update tool again.

If you have not been able to resolve the error code using the steps above or if you are unsure of your ability to follow these steps on your own, get in touch with a trusted computer repair professional that is familiar with the Update process and the errors associated with it.

Read More
How to Fix 0x0000007B Error

What is 0x0000007B Error?

0x0000007B is the most common Windows stop error. The error is displayed on the blue-colored screen which is also called the blue screen of death. You may receive a 0x0000007B error message during Windows XP setup or while running the setup program. The message is often displayed as ‘a problem has been detected and Windows has been shut down to prevent damages’ or ‘inaccessible boot device error’.

Solution

Restoro box imageError Causes

The 0x0000007B error code is usually triggered by:
  • Poor Window XP installation
  • Registry corruption
  • Device Drivers Issues
  • Boot sector viruses

Further Information and Manual Repair

The 0x0000007B error makes your system vulnerable and reduces its speed significantly. And besides, you can’t run the programs smoothly on your PC either. Therefore, it’s advisable to fix the error right away. To fix and repair the 0x0000007B error successfully, you must first understand the cause of the error. Let’s take a look at all the solutions available to fix the 0x0000007B error.

Cause: Boot Sector Viruses

Solution: If your computer is infected with boot sector viruses, then you will first have to download a powerful antivirus. After downloading the antivirus program, run it on your PC to check your computer for viruses. Delete the viruses found and click the repair option. Sometimes even an antivirus program may fail to remove the virus and repair the system. In such cases, you must repartition and format your hard disk and also reinstall Windows XP.

Cause: Device Driver Issues

Solution: Device driver issues may occur if the boot controller is not properly configured or the driver is not up to date. If device driver configuration is the cause of the 0x0000007B error on your PC, then all you need to do is restart your PC, and while restarting press F8 to go to the advanced boot options. Now choose the ‘Last Known Good Configuration’ option. After selecting it, boot into windows and then perform a system restore. Now go to Device Manager and perform a driver rollback to reinstall the drivers. This will resolve the configuration issues. However, if you need an updated driver, all you need to do go on the web and download software to update the driver. It is advisable to download software from the manufacturer’s website in order to successfully update the device driver.

Cause: Poor Windows Installation

Solution: In this case, you will have to perform a Windows start-up repair. To do this: boot Windows XP from CD. Press ‘enter’ at setup Windows Screen when prompted. Then press R to repair Windows Installation. This procedure will not delete any user data and files. In fact, it will copy only the original Windows files over the bad or existing ones. Some of the best ways to avoid Ox0000007B blue screen errors are
  • To scan for viruses every time you use your PC
  • Never open web pages, emails, or download content that you think looks suspicious because that’s probably a virus.
  • Always keep your computer updated.
Read More
Keyboard folder shortcut in Windows 11
If you are visiting a single folder many times during the day it might be beneficial to place its shortcut on the desktop for easy access. But did you know that you can also set a keyboard shortcut for that same folder shortcut making it available simply by clicking desired key combination? keyboard shortcutIn order to make a keyboard shortcut for the desired folder know that it is available only when you have a shortcut of the desired folder, it cannot be done on the folder itself, only on its shortcut. Now folder shortcut does not need to reside on desktop, you can place it anywhere you like, but it must be a shortcut. So the first step is of course to make a shortcut of the folder that you wish to have access via keyboard key combination and place it where you wish. Once you have done this step, right-click on it and choose properties. Inside properties at the top click on the Shortcut tab and then inside Shortcut Key, press the key combination that you wish to associate with this folder. Confirm with OK and start using fast folder access with your desired key combination.
Read More
Fix WHEA_UNCORRECTABLE_ERROR, 0x00000124
Any modifications in a computer, either big ones or small ones can definitely trigger some errors which is why you have to be careful when you modify the system setting. One of the errors you might encounter when you’ve modified your computer is the WHEA_UNCORRECTABLE_ERROR 0x00000124 Blue Screen Error. According to the error data provided by the Windows Hardware Error Architecture or WHEA, aside from system modifications, you could also encounter this error if your computer has a hardware failure which could be due to a hard drive, RAM, or any other hardware component. In most cases, it is related to physical hardware failures which might have something to do with defective hardware, heat-related, memory as well as a processor that is starting to fail or has already failed. To fix the WHEA_UNCORRECTABLE_ERROR 0x00000124 Blue Screen error, here are some suggestions you have to check out.

Option 1 – Try to perform System Restore

Before you further troubleshoot the problem, you might want to perform System Restore first as the BSOD error might be caused by system modifications. Thus, to undo them, you can use System Restore. Run it using these steps:
  • First, tap the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” in the field and tap Enter.
  • Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
  • After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 2 – Try disabling Overclocking

If overclocking is enabled, you might have to disable it as some users reported that the WHEA_UNCORRECTABLE_ERROR 0x00000124 error started to appear right after overclocking. To disable it, follow the steps below.
  • Go to the Start Menu and open Settings.
  • Next, select Update and Security and go to the Recover tab.
  • From there, click on Restart now in Advanced startup. This will restart your computer.
  • Once you’re in the Advanced startup, go to Troubleshoot and then select the Advanced Options.
  • From there, select the UEFU Firmware Settings.
  • Now click on Restart. Once your computer has restarted, it will automatically open BIOS.
  • From the BIOS, go to the Advanced tab and navigate to Performance and then look for Overclocking.
  • Once you’ve found Overclocking, make sure that it is disabled. If it’s not, then disable it and then save the changes made by tapping the F10 key.
  • Start your computer normally and check if the WHEA_UNCORRECTABLE_ERROR 0x00000124 error is now fixed.

Option 3 – Check your computer’s cooling components and make sure that they are working

It is a known fact that an overheated PC causes system slowdowns and even Blue Screen errors like WHEA_UNCORRECTABLE_ERROR 0x00000124. To fix it, you need to check your computer’s cooling components to see whether they’re properly working or not. Then make sure that you clean them up including the fan and other hardware from dust and other debris.

Option 4 – Use the Windows Memory Diagnostics

Since the problem has something to do with the physical RAM, you need to use Windows Memory Diagnostics. To run it, refer to these steps:
  • Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
  • After that, it will give two options such as:
    • Restart now and check for problems (Recommended)
    • Check for problems the next time I start my computer
  • Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.
Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them.

Option 5 – Update or rollback or disable concerned device drivers

To fix the WHEA_UNCORRECTABLE_ERROR 0x00000124 error, you can also try to roll back, or update, or disable the concerned device drivers.
  • Open the Devices Manager from the Win X Menu.
  • Then locate the device drivers particularly the ones that are under the sections of Keyboard, Mouse, USB, and HID Drivers.
  • Next, right-click on them to open the Properties.
  • After that, switch to the Driver tab and click on the Uninstall Device button.
  • Follow the screen option to completely uninstall it.
  • Finally, restart your computer. It will just reinstall the device drivers automatically.
Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions or disable them.

Option 6 – Try running System File Checker or SFC scan

You could also run System File Checker or SFC scan to fix the BSOD error. It is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.
  • Tap Win + R to launch Run.
  • Type in cmd in the field and tap Enter.
  • After opening Command Prompt, type in sfc /scannow
The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:
  1. Windows Resource Protection did not find any integrity violations.
  2. Windows Resource Protection found corrupt files and successfully repaired them.
  3. Windows Resource Protection found corrupt files but was unable to fix some of them.
  • Reboot your PC.

Option 7 – Try to disable the Digital Driver Signature Enforcement

  • Reboot your computer from the Start menu.
  • Then select the option while pressing the Shift key. This will open the Advanced Boot menu.
  • From there, click on Troubleshoot and select Startup Settings.
  • Now select the “Disable driver signature enforcement” option using the arrow keys on your keyboard and then restart your computer normally.
Read More
Cannot save media from Microsoft Photos
The Microsoft Photos app is a useful tool that allows users to view, edit, as well as create videos on their Windows 10 computers. Although it works just fine most of the time, there are some instances when you might encounter some issues when using it. One of these issues is when you cannot save media from the Photos app after you’ve edited an image. This is most likely related to a permission issue. However, according to some users, they got the error where the edited media file can’t be saved. When you encounter this kind of error, you will see the following error in your Photos app:
“It looks like you don’t have permission to save changes to this file. Try saving a copy instead.”
There are several options you can explore to resolve this error. You can try updating the Microsoft Photos app or verify the ownership of the destination folder. You can also re-register and reinstall the app. For more detailed instructions, make use of the options provided below.

Option 1 – Try to update the Microsoft Photos app

The first thing you can do to fix the problem is to update the Microsoft Photos app.
  • Open the Microsoft Store and click on the three horizontal dots for the menu located on the top right portion of the window to see the options.
  • Next, select Downloads and updates and then click the Get updates button in the top right. This will install any pending updates for all the apps including the Microsoft Photos app using the Microsoft Store.

Option 2 – Try to verify the ownership of the destination folder

The next thing you can do to fix the error is to verify the ownership of the folder because chances are, the location where you’re trying to save the file might not have enough permissions to read and write the file to the disk. Thus, you need to take ownership of the folder by following these steps:
  • Type “command prompt” in the Windows Search bar and then right-click on the relevant search result and select “Run as administrator”.
  • After that, if a User Account Control or UAC prompt appears, just click on Yes to proceed.
  • Next, type and enter this command: TAKEOWN /F <path>
  • Note that the <path> is the location of the folder or file in File Explorer.
  • Now type and enter this second command: ICACLS <path> /grant administrators:F
  • Finally, once the command has been executed, restart your computer and then see if you can now access the folder or file.

Option 3 – Try resetting the Photos app

If the first option of restarting the background process of the Photos app didn’t work for you, you can try to reset the Photos app so that it will use the default factory settings. Note that this option works when you are experiencing this issue after making a couple of changes in the Photos app.
  • To get started in resetting the Photos app, open the Windows 10 Settings.
  • Then go to Apps > Apps & features.
  • After that, scroll down until you see the Photos app option – click on it and open its Advanced options.
  • From there, you will see the Reset button, click on it and click and then click on it once more to confirm.
Note: The process may take a couple of minutes to complete. Once it’s done, open the pictures again using the Photos app.

Option 4 – Try reinstalling the Photos app

If none of the first two options given above worked, then you might want to consider reinstalling the Photos app. Unlike what most users think, it isn’t really that hard reinstalling preinstalled apps as you have the Windows PowerShell for that. To use this program in reinstalling the Photos app, follow these steps:
  • Open the Windows PowerShell program with admin privileges and key in the following command:
Set-ExecutionPolicy Unrestricted
  • After that, execute this second command to re-register and reinstall the Microsoft Photos app.
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}
Note: In the command given, do not forget to replace the “PackageFullName” with the actual package name for the Photos app. After executing the command, it will uninstall the Photos app from your computer so you need to install it again from the Windows Store by simply looking for it. Once you found it, just click on install to start the installation process.
Read More
Fix Windows Sandbox failed to start 0x80070015
As of late, many users reported getting an error in Windows Sandbox that has an error code of 0x80070015. According to users, they encountered this error when they tried to start Windows Sandbox. Based on the error code, it seems that there are some problems with the supporting services of Windows Sandbox that trigger the error. It is possible that these services are misconfigured or that they are outdated and have to be updated. Here’s the complete message of the error:
“Windows Sandbox failed to start. Error 0x80070015. The device is not ready. Would you like to submit feedback about this issue?”
If you are one of the users who encountered this kind of error in Windows Sandbox, then you’ve come to the right place as this post will help you sort this problem out. All you have to do is follow each one of the options provided below.

Option 1 – Make sure that all the supporting processes and services of Windows Sandbox are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:
  • Tap the Win + R keys to launch the Run utility 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 following services in the given order:
    • Network Virtualization Service: (Startup type: Manual)
    • Virtual Disk: (Startup type: Manual)
    • Hyper – V Virtual Machine: (Startup type: Manual)
    • Hyper – V Host Compute Service: (Startup type: Manual)
    • Container Manager Services: (Startup type: Automatic)
  • After you find the aforementioned services, restart each one of them.
  • Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 2 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox Error 0x80070015.

Option 3 – Try to run Windows Sandbox as an admin

  • In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
  • Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
  • Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
  • You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given option below.
Read More
What to do if Windows is stuck in Tablet Mode
To make the Windows 10 operating system a lot more user-friendly, Microsoft introduced the Tablet Mode for Windows 10 devices, especially the 2-in-1 devices like Surface Pro and Surface Book. Despite the Tablet Mode’s efficiency, it also encounters some errors from time to time. One of the issues users reported about tablet mode is that they can’t turn off or exit tablet mode. If you are one of these users, read on as this post will guide you in what you can do to fix the issue. To fix the problem with Tablet Mode, there are several suggestions you can check out. You can try to check the full-screen setting, or perform a full shutdown or perform two buttons to restart the Surface devices. You could also disable Tablet Mode via Registry Editor or perform System Restore or change the settings in the System tab or the Action Center.

Option 1 – Try to check the full-screen setting

  • Tap the Win + I keys to open the Windows Settings app.
  • Then navigate to this path, Personalization > Start.
  • Next, scroll down to toggle off the “Use Start Full Screen” option.
  • After that, restart your computer and see if the problem is fixed.

Option 2 – Perform a full shutdown

  • Open Command Prompt with admin privileges first.
  • Next, execute this command to perform a full shutdown: shutdown /s /f /t 0
  • The command you entered will shut down your computer and once it’s turned off, wait for a couple of minutes and then turn it back on.

Option 3 – Try to perform a two-button restart on your Surface device

  • Tap and hold the power button for about 30 seconds.
  • Then release them after 30 seconds.
  • After that, tap and hold the volume up + the power button for 20 seconds. This will cause the display to flash a few times but you have to keep those buttons pressed until your Surface device is turned off.
  • Wait for a couple of minutes and your Surface will turn back on. This should resolve the problem.

Option 4 – Try to disable the Tablet Mode via Registry Editor

  • In the Start Search, type “registry editor” and right-click on the Registry Editor from the results, and then select the Run as administrator option. This will open the Registry Editor with admin privileges.
  • Next, navigate to this registry key: ComputerHKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionImmersiveShell
  • From there, look for the DWORD named “SignInMode” and double click on it.
  • Set its value to “1” and its base as hexadecimal.
  • After that, click on OK to save the changes made. This will make sure that you are signed in to the desktop mode when you log into your account.
  • Now look for the DWORD named “TabletMode” and double click on it and set its value data to “0” and it's base as hexadecimal.
  • Click on OK to save the changes made and then restart your computer.

Option 5 – Run System Restore

  • Tap the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” in the field and tap Enter.
  • Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
  • After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 6 – Try changing the settings in the System tab or the Action Center

  • Go to Settings and navigate to System > Tablet Mode.
  • After that, scroll down to set the “Use desktop mode” from the drop-down menu under the “When I sign in” section.
  • Now restart your computer and see if the issue is fixed.
Read More
INET_E_RESOURCE_NOT_FOUND
The previous Windows versions all came with Microsoft's browser Internet Explorer. A lot of users love it because not only that it is easy to use. It is also very fast. Users didn’t have to worry about compatibility because it is almost always compatible with its Windows Version. When they introduced Windows 10, they changed the name of the browser from Internet Explorer to Microsoft Edge. It is faster and more user-friendly compared to its predecessors. But after the Creator Update, some experienced receiving the inet_e_resource_not_found error code. In contrary to what everyone expects, you actually don’t have to uninstall and reinstall the Microsoft Edge App. What you can do is reset the browser in your Apps & Features Settings in your Microsoft Settings.

To reset the browser you can follow the steps below:

  1. Click on the Windows icon and go to settings.
  2. Click on Apps and this will bring you to the Apps & Features page. Look for Microsoft Edge from the list of Apps and click on it.
  3. Choose Advance Option
  4. Scroll down then Under Reset, click on repair or reset. When you repair it will fix the existing problem but the data that caused the problem may still be present and can still cause problems. If you click on reset, it will delete all the cache and cookies that are installed in your browser but it will save your Favorites as well as your bookmarks.

Another way to resolve this is by disabling the feature TCP Fast Open on Microsoft Edge. To disable this, go ahead and follow the steps below:

  1. Open the Microsoft Edge browser.
  2. Type in about: flags on the Address (URL) bar.
  3. Under Networking, uncheck the Enable TCP Fast Open.
  4. Close your Microsoft Edge browser and open a new one.
Flushing the DNS also worked for other Users. Sometimes, the error code the inet_e_resource_not_found is caused by a corrupted DNS cache. There are 2 ways to flush your DNS. The first option is to use the command prompt to run the command.
  1. To access the Command prompt or CMD, you can search for it on Cortana or you can click on the Windows icon to access the Programs, scroll down to the Windows System folder and click on it.
  2. A drop-down menu will show up, click on Command Prompt which is the first on the list.
  3. Type in the code ipconfig /flushdns and press enter.
  4. There will be a message that will show that says Windows IP configuration successfully flushed the DNS Resolver Cache
  5. Exit the CMD by typing exit and press enter.
The easiest way to do this is to Press the keys Window + R on your keyboard. Type in ipconfig /flushdns in the search box and hit enter or click on OK. These are only some of the ways to resolve the inet_e_resource_not_found. There are other ways to further troubleshoot this issue such as reinstalling your Wifi Adapter Driver or adjusting the DNS Server Address. But most of the time, users are able to resolve the issue with the steps provided above.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status