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

Fix user account is not authorized
If you encounter an error message saying, “The connection was denied because the user account is not authorized for remote login” when you try to establish a remote connection, read on as this post will help you resolve the problem. This kind of error occurs when the targeted host does not allow you to access that system remotely. Based on the error, you are not authorized to log in remotely which means that you need to obtain the correct permission. There are several potential fixes you can try for this error. You can try to check the Remote Desktop Users group or add users to the Security group or check the Remote Desktop Service itself. Refer to the options provided below for more detailed instructions to fix the “The connection was denied because the user account is not authorized for remote login” error.

Option 1 – Try checking the Remote Desktop Users group

You can encounter this error when the Remote Desktop Users group does not have any permission for your user account that you are using to establish a remote connection. Thus, you need to make sure that your user account is a member of the Remote Desktop Users group. How? Refer to these steps:
  • Tap the Win + R keys on your keyboard and then type “cmd” in the field and tap Enter or click OK to open Command Prompt.
  • After opening Command Prompt, type the “lusrmgr.msc” command and tap Enter to execute it.
  • Alternatively, you can also search for “lusrmgr.msc” in the Start Search and once you’ve opened it, select Users and then double click on your user name to open its Properties.
  • From there, switch from the “General” tab to the “Member Of” tab.
  • Next, if you can’t see any Remote Desktop Users group under the Administrator, you have to add it. To do that, just click on the Add button.
  • After that, on the newly opened window, click on the Advanced and Find Now buttons, respectively.
  • And in the Search results box, double click on Remote Desktop Users.
  • Now click on the OK button to save the changes made and check if you can now connect to a remote host or not.

Option 2 – Try to add a user to the Security group

You can actually block or allow a user from logging on through the Remote Desktop Services. However, if you do not have the right setting, you won’t be able to use this functionality. Thus, you need to confirm this setting. To do that, follow the steps below.
  • In the Start Search, type “secpol.msc” in the field and tap Enter to open the Local Security Policy panel.
  • From there, go to User Rights Assignment.
  • Next, look for a policy named “Allow log on through Remote Desktop Services” located on your right-hand side and then double click on it to open its Properties.
  • If you were not able to find the Remote Desktop Users under Administrator, then you have to add it by simply clicking on the Add User or Group button.
  • After that, enter “Remote Desktop Users” in the blank field and click the OK button to save the changes made.
  • Now restart your computer and try connecting again to the remote host.

Option 3 – Try checking the Remote Desktop Users group

There is a service that’s supposed to be running and needs to be set up correctly for you to connect to the remote host. And so you need to ensure that this service is up and running. To do so, follow these steps:
  • Tap the Win + R keys to launch the Run utility.
  • Then type “services.msc” in the field and hit Enter or click OK to open the Services Manager.
  • Next, look for the Remote Desktop Services and double click on it to open its Properties.
  • After that, go to the “Log On” tab and select the “This account” option and then click on the Browse button.
  • On the next screen that appears, look for the Advanced button and click on it and use the Find Now button to search.
  • You will see “NETWORK SERVICE”. Double click on it and then save the changes you’ve made to the settings.
  • Finally, restart your PC and see if the problem is now fixed.
Read More
A Quick Fix Guide to Error 0x8004060c

What's Error 0x8004060c?

If you use Ms-Outlook. You may experience the malfunction 0x8004060c sooner or later. This malfunction was proven to arise in nearly every MS Outlook variation be it 2010 or 2,000, 2007. The malfunction 0x8004060c hinders your capacity to deliver and get e-mails from and your MS-Outlook account and happens without any forewarning. The error happens when the PST file grows too big and there's almost no memory to handle the increase (Which is rather rare nowadays). Generally, the PST file has about 2 gigabytes upper limit and when you reach that, this error is unavoidable. This error happens when you attempt incorporating data that is fresh into your MS-OUTLOOK Account.

Solution

Restoro box imageError Causes

This malfunction might generate difficulties for you personally as your e-mails vanish and can happen suddenly. The system could also crash at times unpredictably. You may not be able to see fresh notifications and attachments in your e-mail. Also, it's also possible to drop significant contact details. What's more, this malfunction could stop e-mails that are fresh to arrive in your inbox. Therefore, it is undoubtedly a significant issue that has to be repaired immediately. The following may be some of the causes for error 0x8004060c:-
  • This error might occur when OST/PST file got corrupt.
  • OST file becomes inaccessible due to Exchange connectivity or synchronization issue.
  • OST/PST file exceeded its default maximum file size.

Further Information and Manual Repair

In the event that you find the malfunction 0x8004060c at any stage, you should do the repair instead of risking dropping connections and all the significant data in your account. The easiest way to repair this malfunction and to handle this issue would be to download the Restoro. Click here to obtain this fix tool on your computer. After installing, click your mouse's left button after which can use the application. It repairs the error code 0x8004060c in the least period and walks you through the entire repair procedure quickly.
Read More
How to Fix Entry Point not Found Dll Errors

What is ‘Entry Point not found dll’ Error?

Entry Point not found dll errors are common in Windows PC. These errors indicate poor PC maintenance. An entry point is basically the memory address inside the dynamic link library. It contains the call being made. A dynamic link library on the other hand is a collection of small programs which use and request this call to run and load programs successfully on your PC. However, when this process is unable to be executed successfully, you come across ‘entry point not found dll’ error messages.

Solution

Restoro box imageError Causes

Generally speaking, some of the typical causes of ‘entry point not found dll’ errors are:
  • Missing, corrupted, and damaged dll files
  • Registry overloaded with invalid entries
  • Disk fragmentation
  • Viral infection
It is advisable to resolve these ‘entry point not found dll’ errors on your PC immediately because dll errors can cause you a great deal of inconvenience as you may be locked out and unable to access your desired programs. Furthermore, if dll errors are left unresolved, such errors can expose your PC to serious threats like system failure, system damage, corruption, and crash.

Further Information and Manual Repair

Though ‘entry point not found dll’ errors are critical errors but the good news is that these can be easily resolved. To fix dll errors on your PC, you don’t always have to hire a professional technician or be a computer programmer yourself. Here are some of the best DIY (do it yourself) ways to resolve ‘entry point not found dll’ errors on your system:

1. Reinstall the Deleted Program

This method to resolve ‘entry point not found dll’ error code is very basic. It is advisable to uninstall and then reinstall the deleted program to retrieve the missing or deleted dll files. Here’s why: dll files are shared files. There are multiple programs on your PC that may be using one type of dll file to load. Now when you uninstall a program that you no more need on your PC, chances are that it may also delete that particular dll file. And when this happens the other programs supported by the deleted dll file are unable to load. Therefore, in such an event the best way to retrieve the missing dll file is to uninstall the program that displays the errors message and then reinstall it. This will help you restore the missing dll file and run the program successfully.

2. Install an Antivirus and a Registry Cleaner

As mentioned above, ‘entry point not found dll’ errors indicate poor PC maintenance. If you don’t maintain your system, the registry overloads with bad and invalid entries, redundant and obsolete files, junk files and cookies. These files acquire a lot of space which damages dll files and the registry. Furthermore, due to data volume overload and less storage space, files are then saved in different places. This is also known as disk fragmentation. When these files are called, it takes a lot of time for the disk to consolidate fragmented data and execute the function successfully. To resolve these issues, you need to clean and restore the registry. Though this can be done manually it may be slightly complicated and time consuming therefore it is advisable to install and run a registry cleaner.

Restoro.

In addition to this, due to poor PC maintenance, viruses and malware can also enter your system unknowingly through file downloads and phishing emails. These can also damage dll files. To remove viruses and malware from your PC it is important to run an anti-virus. Instead of downloading both tools separately on your system, we recommend Restoro. This is a multi-functional and advanced PC fixer embedded with an intuitive algorithm and a user-friendly interface. It includes multiple utilities including a powerful antivirus, a high functional registry cleaner, and Active X controls and class scanner. It also functions as a system optimizer. By running this software on your system, you can easily scan all registry issues and viruses simultaneously. It repairs the damaged registry and dll files, removes unnecessary files and all types of malicious software. It is compatible with all Windows versions. It is easy to use and high on performance. It is a one-stop solution for all ‘entry point not found dll’ errors on your PC. In just a few clicks you can resolve system errors and optimize your PC performance dramatically. Click here to download Restoro and resolve ‘entry point not found dll’ errors.
Read More
MS Store keeps updating the same apps
As you know, the Microsoft store is a built-in tool in Windows 10 where you can find a variety of applications. It helps users in downloading or updating apps in the system. However, there are instances when you could encounter issues while using it. One of the issues that you could face when using the Microsoft Store app is when it keeps on offering apps you have just updated or when you are not able to update any apps at all. This kind of issue in the Microsoft Store app might be caused by other issues like a damaged Windows Store cache. There are several options you can check out to resolve the problem. You can try to check the registry setting or run the Windows Store apps troubleshooter or clear the Windows Store cache manually or reset its settings. You could also try to re-register the Microsoft Store app. For more details, refer to each one of the options provided below but before you troubleshoot the problem, make sure that you create a System Restore point.

Option 1 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the problem in Microsoft Store. This is a great built-in tool from Microsoft that helps users fix any app issues. To use the Windows Store Apps Troubleshooter, follow the steps below.
  • Tap Win + I keys again to open the Windows Settings panel.
  • Go to Update & Security and then go to Troubleshoot.
  • Under the Troubleshoot section, on your left-hand side, scroll down to find Window Store Apps.
  • Then click on the Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 2 – Try checking the settings in the Windows Registry

The next thing you can do to fix the problem is to check the Registry settings for the Windows Store.
  • Tap the Win + R keys to open the Run utility and type “Regedit” in the field and then hit Enter to open the Registry Editor.
  • Next, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionCurrentVersion
  • From there, look for the DWORD named “CurrentVersion” and make sure that its value data is set to 6.3, but if it’s not then change its value data to 6.3
  • Exit the Registry Editor and restart your computer and then see if it fixed the problem with the Microsoft Store app.

Option 3 – Try to reset the Microsoft Store cache

Just like browsers, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.
  • Right-click on the start button and click on Command Prompt (administrator).
  • Next, type in the command, “exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
  • Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 4 – Try to re-register the Microsoft Store app via Windows PowerShell

  • Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
  • If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
  • Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml
  • Wait for the process to be completed and then restart your computer.
Read More
Fix Windows Activation Error 0xC004F211
If you got an Activation Error 0xC004F211 after having installed or upgraded your Windows 10 PC, then this indicates that some hardware in your computer has changed which’s causing the error to pop up. Windows might not be able to determine if the key is used on a new computer or if it’s still the same one if you have just removed or upgraded old hardware. But worry not for this post will guide you in fixing the Windows Activation Error 0xC004F211 on your Windows 10 computer. When you encounter this error, you will see the following error message on your screen:
“Cannot activate Windows 10. Try activating again later. If that doesn’t work, contact support. Error code: 0xC004F211.”
Note that although hardware changes cause this error, the minor ones don’t really cause any issues with activation, however, if you have made any significant hardware change such as replacing your motherboard, it will most likely cause the activation error. In such cases, the Windows Activation system will treat this as new hardware and you will need a new license for that. Even if your Windows 10 computer has a genuine key, it might still fail to get activated which results in the Windows Activation Error 0xC004F211. Thus, before you do other troubleshooting steps, you need to run the Windows 10 Activation Troubleshooter first. To do so, follow these steps:
  • Go to Settings and then select Activation.
  • After that, click on the Windows Activation and then troubleshoot. This will help you address most of the commonly found activation issues in Windows devices.
In addition, there is an exception offered by Microsoft – if you are connected to a Microsoft account prior to the hardware change, then you can most certainly use the same license key to reactivate Windows 10 again. Microsoft calls this an “Exception path” which should be fixed easily by the Windows Activation Troubleshooter as pointed out earlier. However, if the Windows Activation Troubleshooter isn’t able to resolve the error you can try purchasing a new license. In such rate case, even if you do have a Microsoft account available on your Windows 10 computer, and if Windows was never activated, this solution will not work. And if you haven’t connected your Microsoft account with your Windows 10 computer prior to the major hardware change, then your only option left is to purchase a new license. For you to do that here are some steps you can follow.
  • To purchase a new Windows license, the first thing you have to do is click on the Start button > Settings > Update & Security.
  • From there, go to Activation and select the “Go to Microsoft Store” option.
  • After receiving your new license, you need to go back to Update & Security then go to Activation and select the “Change product key” option.
  • Now update your Windows 10 computer using the new key and it should automatically activate your computer.
  • Next, you have to create a Microsoft account or connect your existing local account to your online account.
  • Once the system links the key and the account, you need not buy a new license in case something like this happens again.
Note: If you are an IT administrator, you need to keep in mind that there is a limit to the number of times you can reactivate Windows on your computer. Moreover, if you don’t see any option to reactivate the license, and it is a work computer, you need to contact your organization’s tech support.
Read More
Steam proton to run Windows games on Linux
Steam protonDespite popular belief, there are a lot of users running Linux OS. Linux offers great security and working environment and 96.3% of the world's top 1 million servers run on Linux. 90% of all cloud infrastructure operates on Linux and practically all the best cloud hosts use it. But gaming on Linux is limited, enter Steam proton a Valve’s gaming solution.

What is Steam proton?

Proton is a WINE fork with some extra capabilities, to play games and run applications not native and not made to run natively under Linux OS. It is supposed to bridge the Gaming issues for PC users and let them more freedom in choosing an operating system to game on.

Find out if your game supports Proton

Although there are a lot of titles that nowadays run natively on Linux some will still need proton in order to run at all and sadly some of them will not be able to run on Linux even via proton but seeing how Valve is busy and it is trying to push its ideas and technology slowly this gap is closing. In order to see how the game you want to play performs and behaves on Linux and proton environment visit https://www.protondb.com/ and find out. As soon as the site loads you will be greeted with statistics and a search option to find out the status of the desired game with one of the given statuses: Borked, Bronze, Silver, Gold, Platinum, and Native. As you probably guessed native means that the game will work on Linux out of the box and borked will probably not work at all. Platinum and gold status means that game will run on proton without any input or tweaks from the user while silver and bronze means that it will work but might need some tweaks in order to make it work.

How to get Steam proton?

In order to run games under proton inside Linux, you will need firstly a Steam client which luckily works naturally on Linux. Unlocking/activating Steam Proton on your Linux-based system is easy. Just head over to Steam > Settings > Steam Play and toggle the option “Enable Steam Play for Supported Titles”. Valve has tested and fixed some Steam titles and you will now be able to play those titles. However, if you wish to go even further beyond, and play titles that even Valve has not tested, toggle the option “Enable Steam Play for all titles”.

Conclusion

Even we are not there yet, native gaming on Linux is gaining a foothold each day. Will Steam’s OS with proton technology be one that will turn the tide from Windows or some other tech we cannot tell but one thing is for sure, more choices mean better products so I am hopeful for a bright future.
Read More
How to Fix Slow file copy speed in Windows 10
We tend to move and copy tons of files on our PCs and mostly, the process of copying or moving files, especially if the file has the size of 1GB or up, tends to take quite long. This may be caused by some issues which is why you face slow copy or move speed. So if you are experiencing this issue on your Windows 10 computer, then read on as this post will give you a couple of solutions you can try to increase the speed in copying or moving files. Follow the given instructions below.

Option 1 – Try to change the USB port

You might want to change the USB port since modern computers have a variety of USB ports. So if your USB drive supports USB 3.0 or 3.1, make sure that you plug it inside a USB 3.0 or 3.1 ports. If you’re not sure which port, just keep in mind that the USB 3 port is usually blue or you can also use your computer’s documentation or manual as a reference to locate it. It may sound nothing but changing the USB port can actually improve the copying or moving speeds drastically so this should be the first thing you can try to speed up the process of copying or moving files.

Option 2 – Update the USB Controller Drivers

  • First, click the Start button and type “device manager”.
  • Then click on the “Device Manager” from the search results to open it.
  • From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.
  • Restart your PC and then click the “Search automatically for updated driver software” option.
You also have the option to update the motherboard and the USB driver from the manufacturer’s official website.

Option 3 – Check for any hard disk errors

  • On your desktop, right-click on the “This PC” or computer icon and then select Manage to open the Disk Management. Here you get to check your drive’s health.
  • Next, click on Disk Management on the left side panel.
  • From there, check the state of your drives. If it shows that all your partitions are healthy then it means all is good and that the problem may have something to do with some physical issues with your hard drive.
You might also want to run the CHKDSK utility to help you fix any issues with your hard disk. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.
  • Open Command Prompt with admin privileges.
  • After opening Command Prompt, execute the following command and hit Enter:
chkdsk /f /r
  • Wait for the process to be completed and then restart your computer.

Option 4 – Try to disable Windows Auto Tuning

Disabling Windows Auto-Tuning can also help in increasing the copying or moving of files in your computer. It is said that this feature improves the performance of programs that receive TCP data over a network by adjusting the receive buffer size dynamically throughput and latency of the link. Thus, if you are trying to copy some data over the network, then the Auto Tuning feature is playing a role here. And in some cases, disabling this feature completely resulted in a lot faster copy speeds over the network.

Option 5 – Try changing the USB Removal Policy

  • First, plug your USB drive or external device into your PC and then open This PC.
  • Next, right-click on your device and select Properties.
  • After that, go to the hardware tab and select the storage media that you want to enhance and then click on the Properties button.
  • From there, you can select the Better performance option if you wish for your device to have a better performance. Once you select this option, it will enable write caching in your Windows 10 computer but you need to use the “Safely Remove Hardware” option from the notification area to safely disconnect the device otherwise it may result in data corruption.

Option 6 – Format your drive

  • To get started formatting your drive, tap the Win + E keys and then go to the access page of the drive.
  • Next, right-click on the drive and select Format.
  • After that, uncheck the “Quick Format” option and then format your drive properly.
  • Now once the formatting process is finished, unplug the drive and plug it back in afterward.
  • Check if the error is already fixed. If the drive is not initialized, tap the Win + R keys and hit Enter.
  • After opening the Run dialog box, type “diskmgmt.msc” and hit Enter to open Disk Management.
  • From there, right-click on the drive volume and select initialize disk.
  • Next, select the correct partition type and proceed.
Read More
Fix CLOCK_WATCHDOG_TIMEOUT in Windows
If you encounter the CLOCK_WATCHDOG_TIMEOUT Blue Screen of Death error while using your Windows 10 computer then it is most likely caused by a specified processor which is not processing interrupts. This occurs when the processor is deadlocked or nonresponsive. Specifically, this kind of Stop error occurs when the processor is having a hard time with the cooperation of its threads and cores. The threads are the tasks performed by cores and some cores can have many threads at the same time. And this is where the problem begins – one thread is waiting for an adequate response from another thread or one kernel is waiting for a response from another kernel and those responses are not coming. In other words, when the processor is unable to continue the processing of tasks since its resources are occupied and are interdependent to get free, such a state is called Deadlock. The CLOCK WATCHDOG TIMEOUT bug check has a value of 0x00000101 which means that an expected clock interrupt on a secondary processor, in a multiprocessor system, was not received within the allocated interval. To troubleshoot the problem, you can check out the possible fixes provided below but before you proceed, make sure that you boot your computer into Safe Mode with Networking only.

Option 1 – Undo or disable overclocking if you have overclocked your system

  • 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 CLOCK_WATCHDOG_TIMEOUT 0x00000101 error is now fixed.

Option 2 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the CLOCK_WATCHDOG_TIMEOUT 0x00000101 Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:
  • Tap the Win + R keys to open Run and type mdsched.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.

Option 3 – Try to rollback, update or disable drivers

The next thing you can do to fix the CLOCK_WATCHDOG_TIMEOUT 0x00000101 Stop error is to roll back, or update, or disable device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.
  • Open the Devices Manager from the Win X Menu.
  • Then locate the device drivers and 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.

Option 4 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like CLOCK_WATCHDOG_TIMEOUT 0x00000101. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:
  • Tap the Win + I keys to open the Settings panel.
  • Then go to Update & Security > Troubleshoot.
  • From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 5 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the CLOCK_WATCHDOG_TIMEOUT Blue Screen error.

Option 6 – Troubleshoot the BSOD error in Clean Boot State

You can also troubleshoot the Blue Screen error in a Clean Boot state. There are times when third-party applications cause BSOD errors. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.
  • Log onto your PC as an administrator.
  • Type in MSConfig in the Start Search to open the System Configuration utility.
  • From there, go to the General tab and click “Selective startup”.
  • Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
  • Next, click the Services tab and select the “Hide All Microsoft Services” check box.
  • Click Disable all.
  • Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And to configure Windows to use the usual startup, just simply undo the changes.)
  • From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 7 – Try to update the BIOS

Updating the BIOS can help you fix the CLOCK_WATCHDOG_TIMEOUT BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “msinfo32” in the field and press Enter to open System Information.
  • From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
  • After that, you should see the developer and version of the BIOS installed on your PC.
  • Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
  • If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
  • Now double click on the downloaded file and install the new BIOS version on your computer.
  • Now restart your computer to apply the changes made.
Read More
Fix Windows Update error 0x80246008
Updating your Windows 10 computer does not always go smoothly as there are some errors you can encounter along the way. One of these Windows Update errors is the error code of 0x80246008. This kind of error can occur during different phases of an update that’s being downloaded or installed and even when an update is being initialized. If you narrow down the cause of this Windows Update error, you’ll most likely see that it is related to the deliverability of a file to a computer from the servers of Microsoft. In other words, the error might be due to conflicts from programs like Firewall as well as third party programs like Antivirus or it could also be due to corrupted disk image or system files or it could be that any of the supporting Windows Update components and services are not working properly. Whatever the cause may be, the potential fixes provided in this post can be applicable to Windows Updates as well as the Microsoft Store. Refer to the suggestions provided below to resolve the Windows Update Error 0x80246008 but before you proceed, make sure that you create a System Restore point first.

Option 1 – Apply some tweak in the Windows Registry from Command Prompt

  • Tap the Win + X keys and select Command Prompt (Admin) to open Command Prompt with admin privileges.
  • Next, navigate to the root location of the bootable device inside the Command Prompt command line.
  • Once you’re in the root location, type the following command and tap Enter to execute it:
reg add HKLMSYSTEMCurrentControlSetControlBackupRestoreFilesNotToBackup
  • After that, close the Command Prompt command line and then tap the Win + R keys to open Run utility.
  • In the field, type “services.msc” and click OK or tap Enter to open the Windows Services Manager.
  • From there, look for the following services:
    • Windows Update – Manual (Triggered)
    • Background Intelligent Transfer Service – Manual
  • Now open their Properties and make sure that their Startup type is as mentioned above and that they are running. If they are not running, just click on the Start button.

Option 2 – Run the System File Checker Scan

If the registry tweak didn’t work, you can run a System File Checker scan instead. It is a built-in command-line utility that replaces bad and corrupted system files to good system files that might be the cause why you’re getting the error when you try updating your computer. 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.
  • Restart your computer.

Option 3 – Run the Windows Update Troubleshooter

If the System File Checker wasn’t able to resolve the Windows Update error, you could also try running the Windows Update Troubleshooter as it could also help in fixing any issues related to Windows Update including this one. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 4 – Try to disable your antivirus program

Disabling the antivirus program or any security software installed in your computer is always a good idea you can try when the Windows Update process does not go smoothly. So before you try updating your computer again, make sure to disable the antivirus or security program and once the Windows Update is done, don’t forget to enable the antivirus program back again.

Option 5 – Try deleting the files from the SoftwareDistribution folder and resetting the Catroot2 folder

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.
  • Open the WinX Menu.
  • From there, open Command Prompt as admin.
  • Then type in the following command – don’t forget to hit Enter right after typing each one of them.
net stop wuauserv net start cryptSvc net start bits net start msiserver
  • After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
  • Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:
  • Type each one of the following commands.
net start wuauserv net start cryptSvc net start bits net start msiserver
  • After that, exit Command Prompt and restart your computer.
Read More
Fix Windows Error Code 0x80070017
If you suddenly encountered a Windows Error Code 0x80070017 during an Update, Installation or System Restore then it’s probably due to some missing or corrupted system files. This kind of error code can occur during an update, installation, or system restore and the only way out of it is to download the file once again and re-run the installation from the top. Before you start to troubleshoot the problem, you need to create a System Restore Point first. After you create a System Restore point, you can follow the troubleshooting options laid out below to fix the Windows Error Code 0x80070017. You just have to follow the troubleshooting option that applies to your situation and whether you got the error during an update, installation, or during System Restore. Whether you got the error 0x80070017 while updating Windows 10 or installing it or during a system restore, the first thing you must do is run the System File Checker. As pointed out early on, the Windows Error Code 0x80070017 might be caused by corrupted or missing system files so the first thing you can try is to run the System File Checker scan.
  • Tap Win + R to launch Run.
  • Type in cmd in the field and tap Enter.
  • After opening Command Prompt, type in sfc /scannow and hit Enter.
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.
If you have encountered Windows Error Code 0x80070017 during an Update, then here are some options you need to try:

Option 1 – Delete the files/contents in the SoftwareDistribution Folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. A lot of users tried deleting the files in this folder to fix the problem and so far it has worked. Like them, you can try clearing the Windows Update cache by simply deleting the contents of the folder named “SoftwareDistribution” since Windows apparently can’t clear and re-download the update contents once they are corrupted. Thus, deleting the contents of this folder will make Windows download the contents again which will fix the problem. To do that, follow the steps below.
  • Open the WinX Menu.
  • From there, open Command Prompt as admin.
  • Then type in the following command – don’t forget to hit Enter right after typing each one of them.
net stop wuauserv net stop bits
  • After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
  • Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
  • Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.
net start wuauserv net start bits
Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Option 2 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update Error Code 0x80070017. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go. On the other hand, if you got the error code 0x80070017 during a Windows 10 installation, then it’s because of bad media or corruption in ISO. Here are some troubleshooting steps for this kind of situation:

Option a – Try to create Windows 10 ISO media again

In this option, you will have to create a Windows 10 bootable media and use it to install the latest Windows 10 version. Most users reported that this option works and the reason why it does have something to do with the Windows Update client since the Windows Updates downloaded from the regular Windows Update client seem to create issues such as the error 0x80070017. However, issues like this one don’t occur when the very same Windows Updates are downloaded and installed via an ISO file. Take note that when using a Windows ISO file, you will be asked to choose what you want to do with the previous settings and apps. A lot of users opted for the “Not to keep the old Windows settings” option which has resolved the issue. So if you want to keep the previous settings then you must try to update Windows first while keeping the old settings. However, if it doesn’t work, you have to try installing the latest version of Windows without keeping the previous settings.
  • Click this link and then click the Download Tool Now button.
  • Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
  • Now select the ISO file option in step 5.
  • After that, you should now have an ISO file.
  • Next, go to the location where you’ve downloaded the ISO file.
  • Then right-click on the Windows 10 ISO file and select the Open with the option and then select File Explorer.
  • Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option b – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows update error 0x80070017. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically. If you got the error during System Restore then this means that the files that are being copied from the disk are not making it to the hard drive. To resolve it, here’s what you can do:

Option 1 – Run System Restore in Safe Mode

You might want to run System Restore in Safe Mode and see if it works. Just reboot your PC into Safe Mode and then run System Restore.

Option 2 – Reset Repository

  • Boot your PC into Safe Mode.
  • Then open Command Prompt as admin.
  • Next, type the “net stop winmgmt” command and hit Enter to stop the Windows Management Instrumentation Service.
  • After that, go to C:/Windows/System32/wbem. From there, rename the repository folder to “repository-old”.
  • Restart your computer.
  • After your computer has restarted, open Command Prompt as admin again and then type the “net stop winmgmt” command and hit Enter.
  • Next, type the “winmgmt /resetRepository” and hit Enter to reset Repository.
  • Restart PC and check if System Restore now works.

Option 3 – Try resetting Windows 10

To fix the error 0x80070017, you can try resetting Windows 10. Doing so won’t get rid of any file in your system – instead of erasing all your media files and documents, it only resets all the system settings and files. Simply go to Settings > Recovery. From there click the Get started button under the Reset This PC section.
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