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
Privacy Policy | Terms of Use | Uninstall
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

Facebook
Twitter
YouTube

You might also like

How to Fix Remote Computer requires network level authentication Error in Windows 10
A couple of Windows 10 users have reported an error on domain-connected systems when they tried accessing their computer systems remotely. This occurs when the network level authentication or NLA is enabled on the computer. If you are one of these users, you better keep reading as this post will guide you on how you can fix this error. To resolve this issue, there are several workarounds you can try. You can either disable this option directly via properties or you can also modify some registry entries or sub-keys and restart the system. When you encounter this problem, an error message pops up that states:
“The remote computer that you are trying to connect to requires network level authentication (NLA), but your windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.”
Or you could also see this error message instead:
“The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support.”
Before you proceed in troubleshooting the problem using the options provided below, you need to create a backup for your data or system restore point as well as make a copy of any registry entries you are going to modify.

Option 1 – Disable Network Level Authentication via Properties

The NLA is a useful tool that provides your computer with extra security and helps network administrators in controlling who can log into the system with just a click of a single box. However, there are times when it can become a disadvantage and could prevent you from accessing your system remotely. Thus, you need to disable it using Properties.
  • Tap the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” and tap Enter to open System Properties.
  • Next, go to the remote tab and uncheck the checkbox for the “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” option.
  • Now click the Apply button to save the changes made and exit System Properties and then try logging into the remote computer again and see if the problem is fixed or not.

Option 2 – Disable NLA via Registry Editor

Note that you can only use this option if the first one didn’t work for you. Take note that this option will require you to restart your PC completely which could mean some downtime if your computer is running a production server. So make sure to save all your work.
  • Tap the Win + R keys to open the Run dialog box and then type in “Regedit” in the field and tap Enter to open the Registry Editor.
  • From there, click on File > Connect Network Registry and input the details of the remote computer and then try to connect.
  • Navigate to the path below after you’re connected:
HKLM >SYSTEM > CurrentControlSet > Control >Terminal Server > WinStations > RDP-Tcp
  • After that, change the values given below to “0”
    • SecurityLayer
    • UserAuthentication
  • The navigate to PowerShell and execute this command – restart-computer

Option 3 – Disable NLA via PowerShell

PowerShell allows you to tap into the remote computer and once you’ve targeted the machine, you can execute the commands given below to disable NLA.
  • Tap the Win + S to open Search and then type in “PowerShell” in the field. Right-click on the related result and select the “Run as administrator” option.
  • After opening PowerShell, execute the command below:
  1. Once in the PowerShell, execute the following command:
$TargetMachine = “Target-Machine-Name” (Get-WmiObject -class “Win32_TSGeneralSetting” -Namespace rootcimv2terminalservices -ComputerName $TargetMachine -Filter “TerminalName=’RDP-tcp'”).SetUserAuthenticationRequired(0) Note: In the command given, the “Target-Machine-Name” is the name of the machine you are targeting.

Option 4 – Use the Group Policy Editor to disable NLA

Another option you can use to disable NLA is via the Group Policy Editor. This is ideal for you if you are blanket disabling. Just take note that the Group Policy Editor is a powerful tool and that if you make some mistakes by changing values you have no clue about, you can render your computer useless so make sure that you create a backup for all the values before you proceed.
  • Tap the Win + R keys to open the Run dialog box.
  • Then type in “gpedit.msc” and tap Enter to open the Group Policy Editor.
  • From there, go to this path – Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
  • After that, search for “Require user authentication for remote connections by using Network Level Authentication” and set it to disabled.
  • Now check if the error is fixed or not.
Read More
Fix Windows Update Error 0x80240020
There are instances when the Windows 10 installation needs interaction before it reaches the file process. And so if you suddenly encounter the Windows Update Installation Failure 0x80240020 error under the Windows Update History, then you need to get it fixed. When you encounter this kind of Windows Update Error, you will see an error message that says, “The operation did not complete because there is no logged-on interactive user”. This error also indicates the “WU_E_NO_INTERACTIVE_USER” code. To resolve this issue, in this post we’ll walk you through a couple of steps but before you get started, know that you don’t have to run any troubleshooter or delete any file just to fix this error since all you have to do is enable one option that can automatically login with your account and complete the installation for you. With that said, just make sure to only try running Windows Update once you’re told to do so. There are two ways you can enable the option that could resolve the Windows Update Installation Failure 0x80240020 error. One is via Settings while the second one is via Registry Editor.

Option 1 – via Settings

Step 1: Go to Settings > Accounts > Sign-in Options. Step 2: From there, toggle on the “Use my sign-in info to automatically finish setting up my device and reopen my apps after an update or restart” option. Step 3: After that, it will make sure that the interaction part is removed from the Windows Update process. Note: If your device is joined in a domain or if some work or email policies are applied to your device by your company or organization, then you wouldn’t be able to see this option in Settings and that’s where the Registry Editor comes in. Just make sure that you’re logged in as an administrator and that you create a System Restore Point first since registry hacks are sensitive and could highly impact how your computer behaves or functions. Once you have that covered, follow the steps below.

Option 2 – via Registry Editor

Step 1: In the Start search, type “Regedit” and hit Enter to open the Registry Editor. Step 2: Navigate to the following registry key:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdateOSUpgrade
Note: If the above-given registry key does not exist, you can simply create it. All you have to do is right-click on the WindowsUpdate key and then select the New Key option and type “OSUpgrade” as its name. Afterward, create a new DWORD (32-bit) Value and name it “AllowOSUpgrade” and set its value to 0x00000001. Step 3: Restart your computer and check if the error is now fixed. And then try to update your Windows 10 computer again and while you’re at it, make sure that you’re around your computer to interact with the prompts needed to complete the installation process.
Read More
Reddit released the application in MS store
Reddit appReddit is one of the most popular websites in the world and how Microsoft is opening doors to everyone in its new store Reddit took a logical step and made a Progressive web application and placed it in it. Being a Progressive web app makes it more familiar and feels like a home experience using it for a lot of Reddit users. Reddit itself has a large community and active topics discussions all the time about anything. Bringing it to Windows as an application is, in my opinion, a great move since as an application it is independent, more light-weighted, and offering some other advantages specifically tied to being a standalone windows application. Everyone familiar with and using the Reddit website will feel right at home in this app and you can start using it right away.
Read More
Start Search is not displaying results
If you have just installed the latest Cumulative Update on your Windows 10 computer and you find that since then, the Windows 10 Start Search is not displaying any results when you try to use it to search for something in your computer, then this post might help as it will give you some suggestions to fix the problem. This problem might be caused by some bugs brought in by the new cumulative update you’ve installed. It is also possible that Cortana is having some issues or that the Windows Search service hasn’t been initialized. Whatever the cause is, here are some suggestions you need to follow to fix this issue. You can try running the Search and Indexing troubleshooter or configure the
  1. Run Search and Indexing Troubleshooter
  2. Configure the Windows Firewall
  3. Reinstall Cortana.

Option 1 – Try to run the Search and Indexing troubleshooter

The first thing you can do is to run the Search and Indexing troubleshooter in Windows 10 as it checks whether the settings for Cortana are in place and automatically corrects any issues if the update or software installation has changed the settings. To run it just click on the Start button and select Settings > Updates and Security > Troubleshoot. From there, select the Search and Indexing Troubleshooter.

Option 2 – Restart Cortana’s process in the Task Manager

Restarting Cortana’s process in the Task Manager could also help you resolve the problem. Refer to the steps given below to do so.
  • Tap the Ctrl + Alt + Del keys to open the Security options window.
  • From there, look for the Task Manager in the given list and open it.
  • Next, look for the process of Cortana and right-click on it, and then select the End Task option to end its process.
  • After that, the Cortana process will restart by itself and re-initialize.

Option 3 – Try resetting Cortana

  • Open Cortana and go to the Settings section where you’ll see the “Turning off Cortana clears what Cortana knows on this device, but won’t delete anything from the Notebook. After Cortana is off, you can decide what you’d like to do with anything still stored in the cloud” option. Turn this option off.
  • Restart your PC.
  • After your computer boots, launch Cortana again and check.

Option 4 – Try to configure the Windows Firewall

  • Tap the Win + Fn + Shift (Pause) keys to open Control Panel.
  • From there, open the Windows Defender Firewall applet and click on the Advanced Settings to open the Windows Firewall with the Advanced Security panel.
  • Next, click on the Outbound Rules section and look for Cortana and then double click on it to open its Properties.
  • After that, make sure that the “Allow the connection” is selected although this is the default working setting.

Option 5 – Try to reinstall Cortana

If none of the options given above works, you must consider reinstalling Cortana.
  • First, right-click on the Taskbar and select the Task Manager.
  • Next, select File menu > Run new task and type “Powershell” in the field and then select the “Create this task with administrative privileges” option.
  • Click on OK to open the PowerShell console.
  • After that, type the following command and hit Enter to execute it:
Get-AppXPackage -Name Microsoft.Windows.Cortana | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}
  • Restart your computer and check if the Windows Start Search is now working.
Read More
Fix Memory error 0x0000001A on Windows
One of the hardest issues you can encounter on your Windows computer is the Blue Screen of Death error. There are various kinds of BSOD or Stop errors and one of them is the “Memory Management Error 0x0000001A” error. This kind of Stop error might signify a hardware problem in your computer and is most likely caused by an issue with RAM or hard disk or even malware that takes up all your computer’s memory, thus, making it crash and display a BSOD error like the Memory Management Error 0x0000001A. Moreover, this kind of Stop error can also occur during the Windows upgrading process. So in this post, we’ll show you what you can do to fix the Memory Management error on your Windows 10 PC.

Option 1 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that 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 2 – Update the device drivers

  • Tap the Win + R keys to launch Run.
  • Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
  • After that, a list of device drivers will be displayed. Look for the device driver you and then select either “Update driver” or “Uninstall device”. And if you find any “Unknown device”, you need to update it as well.
  • Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
  • If you have chosen to uninstall the driver, follow the screen options to complete the process and then restart your PC.
  • Connect the device and Scan for hardware changes – you can see this option under Device Manager > Action.

Option 3 – Run the Windows Memory Diagnostics Tool to test RAM

Since the issue concerns the memory of your computer, you can also try running the Windows Memory Diagnostics Tool to find out if the RAM module of your computer has become corrupted. To run this tool, follow these steps:
  • Tap the Win + S keys to open Search.
  • Then type “Windows Memory Diagnostics Tool” in the field and hit Enter to open the Windows Memory Diagnostics Tool.
  • After that select any of the following option from the prompt that appears:
    • “Restart now and check for problems (recommended)”
    • “Check for problems the next time I start my computer”
  • After that, if you find that your RAM is corrupted, you might have to purchase a new one or change the motherboard of your computer.

Option 4 – Run the DISM tool

There are cases when the Memory Management Error 0x0000001A error is caused by the Windows System Image so you need to repair it using the DISM or Deployment Imaging and Servicing Management tool. The DISM tool is another command-line tool in the Windows operating system that could help users fix various corrupted system files. To use it, follow these steps:
  • Open the Command Prompt as admin.
  • Then type in this command: Dism /Online /CheckHealth
  • Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 5 – Run the SFC scan

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

Option 6 – Try using System Restore

You can also try to perform a System Restore as it can also help you fix the BSOD error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.
  • 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.
Read More
DDR5 what we know so far about it
DDR5 memory moduleNext-generation of RAM, DDR5 supposed to hit shelves around late summer or fall in 2021if everything goes as planned. Its goal is to increase speed and efficiency, wants to pack more memory in a single stick, and have better power management.

Hardware requirements for DDR5

Using the latest memory technology will require other hardware to follow certain standards and the first ones that will need to follow are CPUs and Motherboards. Intel is already prepared with its Alder Lake CPUs that suppose to come out also later this year. AMD on other hand has not stated anything at the time of this writing but it is a bet that their next generation that will come in 2022 will have full support. It is speculated that bot companies and their respective CPUs will have both support for DDR4 and DDR5. A story about motherboards is a little different. Motherboards will support DDR4 or DDR5 memory banks, not both, so make sure that your motherboard will support the memory you plan on getting.

Capacity of memory

The goal and aim for the DDR5 memory stick are to reach a whopping 126GB per stack. This will be done by using a dual in-line module or DIMM enabling larger capacity. That being said, the first modules that we will see are more likely to be 16GB as standard and 8GB as low entry ones.

Power consumption of DDR5 memory

The standard voltage that DDR4 operates under is 1.2V. DDR5 wants to lower this to 1.1V without sacrificing speed. Voltage regulation on modules themselves will be now integrated on memory banks instead of leaving that to motherboards which will help to detect memory errors directly on the memory bank.

Speed of memory

The most common speed of DD4 memory banks is 2,666MHz, more expansive ones go from 3,600 to 4,000MHz. DD5 aims to raise this bar to 4,800MHz and offers greater speed.

Should you get it right away?

Hardware is ever-evolving, we have PCIe 3.0 to PCIe 4.0, and taking into account that sometimes the newest tech can cause some unexpected behavior it is always the best strategy to wait for a little. Price for the newest tech has also been in its heist just when it is released and seeing how DDR5 will benefit mostly servers mostly since even today memory, processors, and other available equipment can tackle all daily tasks.
Read More
A Quick Guide to Fix Error 0x0000001e
Error 0x0000001e is when you start the Windows XP Setup and you see a message which says something like: STOP: 0x0000001E (0x80000003, 0xBFC0304, 0x0000000, 0x0000001)

Solution

Restoro box imageError Causes

You are most likely to face this error if you restart your PC while the Windows Setup is still under process and yet to complete. Other causes of this error include any of the following conditions:
  1. The drive on which you are installing Windows has insufficient disk space to accommodate the installation.
  2. An incompatible or outdated third-party driver (or more) is installed on your PC which is conflicting with the installation. For instance, this could be a problematic video driver.
  3. The system BIOS has incompatibilities with the installation.

Further Information and Manual Repair

This error is also called the “Bug check code”. The STOP 0x1E signifies that there was an unknown or illegal processor instruction detected by the Windows XP kernel. You will see the exception address which shows up to indicate the root of the problem which is usually a driver or faulty hardware. You should note this address down as well as the link date of the faulty driver or image which includes it. If at any point it becomes impossible for you to handle and you end up contacting the Windows support center to help you out with the process then this information will help you out in making things a lot easier while the support team tries to troubleshoot the problem. The parameters included in the STOP 0x1E error message are the following:
  1. is the exception code which couldn’t be handled.
  2. shows the module’s address where the exception took place.
  3. signifies the exception’s parameter 0.
  4. represents the exception’s parameter 1.
You can use this information which usually is provided in error 0x0000001e message to pinpoint the root cause of the problem and troubleshoot it. In order to fix this error, you need to follow either one of the following procedures as needed according to your situation.

Clean Up Your Disk

local disk propertiesIf your disk doesn’t have ample space to accommodate the installation then you should free up some of the space on your disk to make sure the Windows can be installed on it. You can also reinstall the Windows on another disk that has sufficient space.

Get Rid of the Third Party Driver

If the error 0x0000001e message gives you the name of the driver due to which the installation process is being halted, then get rid of that driver by disabling it or removing it. If the problem is resolved by this then you should contact the manufacturer of the third-party driver and ask them about any newer versions of the driver that wouldn’t conflict with the installation of Windows.

Upgrade System BIOS

Upgrading your system BIOS is something that you can’t do on your own. You will need to find out more about how you can upgrade. For this, you should contact either your PC’s manufacturer or your motherboard’s manufacturer. If nothing else works, you can always make use of the Microsoft Debugging Tools which will provide you ample information about the error message. You will find the Debugging Tools and further information about them including the downloading and installation process on Microsoft’s website.
Read More
Fix SPECIAL POOL DETECTED MEMORY CORRUPTION
If you suddenly encounter the SPECIAL POOL DETECTED MEMORY CORRUPTION Blue Screen error with a bug check value of “0x000000C1” while you are using your computer then it might be due to some problem with the hardware of your Windows 10 computer. According to security experts, it is most likely caused by the physical RAM which could be due to some error in the Realtek driver for Wireless USB 2.0 as well as corruption of the files inside the RAM, and so on. This kind of problem indicates that the driver wrote to an invalid section of the special pool. On the other hand, system files like the rtwlanu.sys or nvlddmkm.sys can also trigger the SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION Blue Screen error. To resolve this Blue Screen error, you can use the options provided below as reference but before you do that, make sure to create a System Restore point first. After you have that covered, proceed to the given options below.

Option 1 – Delete the settings of the Driver Verifier Manager

  • Open the Driver Verifier Manager using the Start search.
  • After that, select or click on the “Delete existing settings” option and then click on Finish.
  • Reboot your computer and see if it fixes the Blue Screen error or not.

Option 2 – Try to update or rollback your Network driver

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:
  • Tap the Win + R keys to launch the Run window and then type in the “msc” command and hit Enter to open the Device Manager window.
  • Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
  • From the list of Network Drivers, look for “Realtek <Model> Wireless LAN 802.11n PCI-E NIC” and then right-click on it and select Update Driver.
  • Restart your PC and see if it helped in fixing the BSOD error.
Note: If you see any of the following entries under the Network drivers, you might want to download their latest available versions from each one of their manufacturer’s websites.
  • Realtek High-Definition (HD) Audio Driver
  • Realtek Card Reader Driver
  • Realtek Local Area Network (LAN) Driver
On the other hand, if updating the Network driver didn’t help, you can also try to roll back to its previous version.
  • Open the Device Manager again and then look for Network Drivers.
  • Next, select Realtek <Model> Wireless LAN 802.11n PCI-E NIC from the list of Network Drivers and then double click to open a new mini window.
  • After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of the Realtek driver.
  • Now restart your computer to successfully apply the changes made.

Option 3 – Try running the ChkDsk utility

You can also run the ChkDsk utility to fix the SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION Blue Screen error.
  • First, open This PC and right-click on your operating system partition for Windows.
  • Next, click on Properties and navigate to the Tools tab.
  • Then click on Check under the Error Checking section.
  • After that, a new mini window will be opened and from there click on Scan drive and let it scan your disk drive partition for any errors and then restart your computer.

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 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION. It can be found in 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.
Read More
Makecab.exe is running & consuming CPU
The Makecab.exe process that’s running on your Windows 10 computer is a program that compresses the Component-Based Servicing log or CBS log files and they can get really huge if they’re not compressed. As a result, it would utilize important space on your operating system although makecab.exe does not consume high CPU resources in doing so. However, there are times when it recreates thousands of instances of itself and could cause overconsumption of system resources which slows down your computer. So when the makecab.exe process causes high CPU usage in your system, this could mean that there is a failed Windows Update. In addition, the high CPU usage of the makecab.exe process could also mean that your computer is infected with a virus or malware. Whichever the case is, you can check out several possible solutions that are given in this post to resolve the problem.

Option 1 – Try to delete log file using File Explorer

The CBS log files could reach up to 20GB size and so if you delete them, it would help in saving space in your computer and since they’re not much of use, deleting them won’t negatively affect the system at all. To delete the CBS log files, all you have to do is open the File Explorer and then go to C:/Windows/Logs/CBS and from there, open the CBS log files and delete them all. Doing so should ease the load in the makecab.exe process since it no longer has to compress the CBS log files. As a result, the process would be more relaxed. After that, you can restart your computer and check if the problem’s now fixed.

Option 2 – Try deleting the log file via Command Prompt

You can also try to delete the log files using an elevated Command Prompt. Refer to these steps to do so:
  • Type “command prompt” in the Windows Search bar and then right-click on the related search result and select the “Run as administrator” option.
  • Next, type the following command and hit Enter to execute it:
del /f %windir%logscbs*.log
  • Restart your computer afterward once the command has been executed. This should end the high disk usage by makecab.exe, if not, proceed to the next given options below.

Option 3 – Uninstall any suspicious programs you’ve installed recently

If you have recently installed some programs on your Windows 10 computer, and since then you’ve experienced high CPU usage brought on by makecab.exe, then you might want to uninstall those programs.
  • Tap the Win + R keys to open the Run dialog box
  • Then type “appwiz.cpl” in the field and hit Enter to open the Programs and Features in Control Panel.
  • From there, look for the suspicious programs you’ve installed, select them and then click on Uninstall to remove them.
  • After that, restart your computer and try to install the latest version of the program again. It should work now. If not, proceed to the next available option below.

Option 4 – Try running Disk Cleanup

You might want to run the Disk Cleanup utility as it is a useful tool that could delete temporary and useless files on your computer.
  • Tap the Win + R keys to open the Run dialog box and then type “cleanmgr” in the field and hit Enter to open the Disk Cleanup window.
  • After that, select the drive you want to clean.
  • Now click OK to clean the disk and restart your computer.

Option 5 – Try to run System File Checker scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files and missing files. It replaces bad and corrupted system files to 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.
  • Restart your PC.

Option 6 – Try scanning your computer using Windows Defender

As mentioned, the high CPU usage of makecab.exe might be caused by some malware or virus in the system and so to eliminate it, you have to scan your computer using security programs like Windows Defender.
  • Tap the Win + I keys to open Update & Security.
  • Then click on the Windows Security option and open Windows Defender Security Center.
  • Next, click on Virus & threat protection > Run a new advanced scan.
  • Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.
Read More
Fixing Windows Update Error 80244019
As you know, Windows Update is the source for everything latest for Windows from Microsoft. Your computer receives essential updates frequently because of the Windows Update service and this Windows Update mechanism depends on various services such as Background Intelligent Transfer Service or BITS, Windows Server Update Service, Windows Update service, and many more. Although it may seem like a complex delivery system, it is a very efficient one. However, it is not without its issues as it still encounters errors every now and then. One of these errors is 80244019 which applies only to the Windows Server operating systems and to resolve it, you need to determine its cause. The Windows Update Error 80244019 is most likely caused by faulty and corrupted DLL files or Registry Entries, connectivity issues, and outdated configuration of Windows Update service on the client end. Moreover, the error can also be caused by malware or if a file is not found on the server. This error can lead to a number of system issues like Startup and shutdown issues, software installation errors, external devices connection, system lags, unexpected application, and program issues, and many more. To resolve the problem, refer to the options given below.

Option 1 – Restart some Windows Update services

The first thing you have to do is to restart Windows Update-related services. Refer to the steps below to do so.
  • 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 there by 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 – Try turning on the Data Execution Prevention or DEP

The problem might be caused by disabled Data Execution Prevention which is why you have to make sure that it’s turned on.

Option 3 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update Error 80244019. 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 reconfiguring the Windows Update Settings

You can also try to reconfigure the settings in the Windows Update section to resolve the error.
  • Tap the Win + I keys to open the Windows Settings.
  • Next, click on Update & Security > Windows Updates > Update Settings and from there, click on the Advanced Options.
  • After that, uncheck the “Give me updates for other Microsoft Products when I update Windows” option.
  • Now restart your computer to successfully apply the changes made and then check if the Windows Update error is now fixed.

Option 5 – Try to manually install the Windows Updates

Windows Update Error 80244019 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:
  • Go to Settings and from there go to Update and Security > View Update History.
  • Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
  • After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.
Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.
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
en en