Upcoming comic book movies with release dates

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.

Can not open and run EXE file in Windows is not a new issue and sadly it can still happen from time to time, luckily this step by step solution will help you to resolve this problem fast and effective in no time. Try the below solutions in no particular order and I hope that you will solve the issue fast and be able to return to using the computer like it never happened

1. Run SFC scan

   As the EXE file not opening issue lies in the Windows OS, the SFC tool will be able to identify the cause and fix this issue. Press ⊞ WINDOWS + X and choose command prompt (admin) in command prompt type: sfc /scannow Press ENTER

2. Check registry and modify if needed

   Sometimes value in the registry key is wrong and can cause this error, in order to check if this is the case, we will open the registry editor and find out Press ⊞ WINDOWS + R to bring run dialog up type in it: RegEdit and press ENTER In the left pane of the Registry Editor window, click on the HKEY_CLASSES_ROOT to expand the section Scroll down to find out the .exe registry and click on it Go to the right pane of the window and double-click on the Default and set the Value Data as exefile Click on the OK button Next, located the given in the window: HKEY_CLASSES_ROOT>exefile>shell>open>command Click on the “Command” in the left pane of the window In the right pane of the window double-click on the Default and set Value Data as “%1” %* Click on the OK button Restart your computer and check if the issue persists

3. Turn off Firewall and defender

   If you have a firewall and antivirus active there might be a chance of a conflict and that firewall or antivirus is preventing the EXE file from starting, disable your firewall and anti-virus and try again to open the EXE file.

4. Turn off user account control

   User account control can also like a firewall prevent some files from executing, go into accounts and turn off user account control to see if this might be an issue preventing you from opening the file.

There are times when it is really inevitable to delete your hard drive partitions especially if you are already running low on disk space in your Windows 10 computer. Users typically delete the volume which is not being used in such cases in order to free up some space for the volume that’s running low on disk space. To resolve the problem, users tend to use the Disk Management utility to delete hard drive partitions. However, some users reported that the “Delete volume” option is not available as it is grayed out. Thus, users aren’t able to delete hard drive partitions and aren’t able to free up disk space. This kind of problem usually occurs when there is a Page file on the volume that you are trying to delete and so on. Oftentimes, this issue is mistaken for the problem where you are unable to delete an EFI-protected partition. However, in this case, not only you are unable to delete EFI-protected partition but also NTFS file systems. This is really hard to deal with but worries not for there are some potential fixes you can check out to resolve this problem.

Option 1 – Try to manage the Page file in the Partition

As mentioned earlier, if a Page file exists in a partition, you won’t be able to delete it. The page file is what stores your data when the system’s random access memory fills up. To resolve this, follow these steps:

• Go to the Start menu and type “View advanced system settings” in the field and open it from the search results.
• Next, click on Settings in the Advanced tab.
• On the new window that pops up, go to the Advanced tab and select Change.
• Next, uncheck the checkbox of “Automatically manage paging file size for all drives” and highlight the drive you want to delete.
• Then select “No paging file” and click on Set.
• Now click on the Apply and OK buttons on all the windows and restart your computer.

Option 2 – Delete storage partition via Command Prompt

• Tap the Win + X keys or right-click on the Start button and select Command Prompt (Admin) or you could also type in “cmd” in the Cortana search box and right-click on the Command Prompt icon and then select the “Run as Administrator” option from the context menu.
• Once you have Command Prompt pulled up as admin, type in and enter this command – diskpart
• After entering this command, the Diskpart Utility will start. Diskpart Utility is a command-line-based utility just like Command Prompt but it will get a UAC Prompt after you invoke it so you have to click Yes for the UAC Prompt.
• After that, type in list volume and tap Enter to see the list of all the partitions created on your PC. This includes both types of partitions that are visible to the normal users in the File Explorer as well as the ones that are created by Windows 10 by default which helps it in storing the boot files and other essential system files.
• You should see a list of all the partitions made on your computer. Select the partition you want to delete by its Unique Identification number as Volume X where X denotes the Unique Identification Number.
• Next, type in the select volume number command and hit Enter to select the desired volume.
• Then delete the volume you’ve selected and type in the delete volume command and hit Enter to delete the volume you just selected and convert it into unallocated space.

Option 3 – Delete storage partition via Windows PowerShell

• Start by tapping the Win + X keys or simply right click on the Start button and select Windows PowerShell (Admin) or you could also type in “Windows PowerShell” in the Cortana search box and right-click on the Windows PowerShell icon and select the “Run as administrator” option.
• Once you’ve opened the Windows PowerShell, type in the Get-Volume command and hit Enter to get a list of all the partitions on your PC.
• Next, select the drive letter you want to delete and then type in the Remove-Partition –DriveLetter command and hit Enter to delete the selected partition. Note that you need to replace the drive letter with the letter of the partition you want to get rid of.
• After that, it will ask you for confirmation. Just hit the Y key for Yes or hit the A key to say Yes to All. This will delete all the partition you’ve selected and will move them in as unallocated space.

As you know, just like other web browsers, Google Chrome offers Incognito Mode or private browsing which you can use to make sure that your browsing activities are not being tracked by any websites you visit and it also keeps targeted ads at bay. On the other hand, signing in to a website, even when in Incognito Mode is a different thing since that website can track your browsing activities. Thus, Incognito Mode is still useful especially if you want to browse the web safely and without getting tracked except when you log in to some site. However, there have been reports recently that Incognito Mode is missing in Chrome and users are clueless as to how or why it happened. If you are one of them, worry not for this post will walk you through what you can do if there’s no Incognito Mode in Chrome on your Windows 10 computer. This is an unusual and strange issue since the Incognito Mode in Chrome is available by default and you don’t have to do anything to enable it. It is possible that there might be corruption in the Windows Registry which caused the disappearance of Incognito Mode, worry not though for there are some tweaks you can apply to restore the missing Incognito Mode. To apply these tweaks, you need to create first a System Restore point, and then once you’re done, follow the instructions provided below carefully. Step_1: Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and then hit Enter to open the Registry Editor. Step_2: Next, after opening the Registry Editor, navigate to this path – ComputerHKEY_LOCAL_MACHINESOFTWAREPolicies Step_3: From there, look for ChromePolicies and locate the DWORD named “IncognitoModeAvailability” and double click on it. Step_4: Edit the value of the “IncognitoModeAvailability” DWORD by changing its value from 1 to 0 so you can enable Incognito Mode in Chrome. Step_5: Once done, exit the Registry Editor and restart your computer and then check if you can now see Incognito Mode in Chrome. On the other hand, there is also another option that allows you to force open your Chrome browser in Incognito Mode. All you have to do is set the value of the “IncognitoModeAvailability” key to “2” instead of 0. This can be useful especially if you always browse the web in this mode. But you need to remember that you won’t be able to go back to the normal mode once you do this. Here are what the values of the IncognitoModeAvailability DWORD actually mean:

• 0 – Incognito mode is enabled by default
• 1 – Incognito mode is disabled
• 2 – Chrome is forced to always open in Incognito mode

Both the Windows 10 and Windows Server operating systems have a number of common system files that vary from the ones that support the installation, boot process, and other operations or tasks in the system. However, if any of these files get corrupted, it might cause some errors during the setup of the Windows 10 operating system. One of these errors is the “Windows cannot find the Microsoft Software License Terms” error.

“Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation.”

The only option given when you encounter this error is to click on the OK button and nothing else and then the setup gets interrupted and won’t push through. To fix this error and proceed with the installation, you can try to get a new installation image or switch ports, or fix the CFG file. For more details, follow each one of the potential fixes provided below.

Option 1 – Try to get a new installation image

It is possible that there might be some issues with the installation image. It could be corrupted or was modified illegally. Or it could be that the bootable storage device created might have damaged sectors or installation. To resolve this problem, you need to download a fresh copy of the Windows 10 installation image using the Windows Media Creation tool or simply use the ISO image separately and then build a bootable USB.

Option 2 – Try to switch Ports

The error might be caused by the connection to the USB port. It could be that the port is unstable due to a number of factors that resulted in the interruption of the installation process. To fix this problem, you can try switching the USB port or if you are using an optical drive, you can get an external USB optical drive or connect it to another port internally and see if it fixes the problem.

Option 3 – Try to fix the CFG file

If none of the first two options worked, then you might want to fix the CFG file. This file is a configuration file format used for storing settings. All you have to do is download the CFG file. Once you’ve downloaded this file, copy this file to the root of your bootable drive and then check if it fixes the error. If not, then try to copy the same file inside the “/sources/” folder inside the root of the drive. This should fix the error.

As you know, Windows allows you to share files between systems that are on the same network even though they are not connected physically. All you have to do is to make sure that the folder administrator allows access to the intended use and that your computer should be connected to the internet. Once you meet these conditions, you can share files between systems. However, recently a number of users reported that despite fulfilling these conditions, they end up getting errors instead when they try to access the shared drive. The error states:

“Error code: 0x80070035. The network path was not found.”

One of the common causes of this error is the antivirus program or the Firewall installed on your computer. It could also be that the drive is not shared in the first place or there are some issues with your network drivers. Whichever the case is, here are some potential fixes you need to check out to fix the Error code: 0x80070035.

Option 1 – Try to temporarily disable anti-virus and Windows Defender Firewall

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed on your computer. Thus, disabling them or any security software installed in your computer is always a good idea you can try when you’re not able to access the shared drive on your computer. There are times when you encounter problems like Error code: 0x80070035 due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program and Windows Defender Firewall for the meantime and check if it fixes the error or not.

Option 2 – Check if the drive is shared

Before you further troubleshoot the problem, make sure that the drive you are trying to access is shared first. To do so, follow these steps:

• Right-click on the folder and select Properties.
• Go to the Sharing tab and check the status of the Network File and Folder Sharing.
• And if the status is “Not Shared”, you need to select Share.
• Next, select the intended Network User for sharing the file and choose the permission level for the user.
• After that, click on the Apply and OK buttons to save the changes made. You or the intended user should now be able to access the shared folder or file.

Option 3 – Try to ping the IP address of the targeted computer

Even though the shared folder or file is shared correctly, it is possible that the network channel is not connected properly which is why you have to test it by pinging the IP address of the targeted computer from the primary computer.

• Tap the Win + R keys to launch the Run dialog box.
• Type “cmd” in the field and tap Enter to open Command Prompt.
• Next, type the “ipconfig/all” command and tap Enter to execute it. This will populate various details.
• From the given details, take note of the IPv4 address.
• Afterward, open Command Prompt on the primary computer and then type the “ping <IPv4 address of the target computer>” command and hit Enter.
• Now check if you get 4 confirmation replies or not. If not, you can try to access the Network Adapter Troubleshooter.

To run the Network Troubleshooter, refer to these steps:

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

Option 4 – Verify if Network Discovery is enabled

All you have to do is go to Start > Settings > Network & Internet and from there, click on the “Change connection properties” option and shift the radio button for Network profile to Private. After that, check if folder sharing is now working.

Option 5 – Try to modify the Network Security settings

There are times when the Network Security settings interfere with the folder or file sharing process. And if that’s the case, you can modify it to resolve the problem. How? Refer to these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then type “secpol.msc” in the field and tap Enter to open the Local Security Policy manager window.
• After that, go to Local Policies > Security Options located on the left pane.
• Next, double click on Network security: LAN Manager authentication level in the right pane to open its Properties.
• And then select the “Send LM & NTLM-use NTLMv2 session security if negotiated” option from the drop-down menu.
• Now click on Apply and OK buttons to save the changes made.
• Reboot your computer.

Option 6 – Try to enable NetBIOS over TCP/IP

• Tap the Win + R keys to open the Run dialog box.
• Then type “ncpa.cpl” in the field and tap Enter to open the Network Connections window.
• After that, right-click on your network and select Properties.
• Next, double click on Internet Protocol Version 4 and click on the Advanced button.
• From there, go to the WINS tab and shift the radio button to Enable NetBIOS over TCP/IP.
• Now click OK to save the changes made and then restart your computer.

Option 7 – Update the Network Adapter drivers

You might also want to update the Network Adapter drivers by following 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.
• Then right-click on each one of the Network drivers and update them all.
• Restart your PC and see if it helped in fixing the BSOD error.

Note: If updating the network drivers didn’t help in fixing Error code: 0x80070035, you can also try to uninstall the very same drivers and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly. To reinstall the network adapter driver, refer to these steps:

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

When experiencing internet connection problems, most users run the built-in troubleshooter to fix the problem. However, you might come across another problem when instead of fixing the problem, the troubleshooter throws up an error message saying, “The Windows Wireless Service is not running on this computer”. After displaying this error message, the troubleshooter would exit. Usually, this kind of error indicates that Windows has failed to initialize the wireless service so it can start searching for broadcast signals and try to connect to them. So in this post, we have prepared some workarounds that might help you resolve the issue.

Option 1 – Try to check the WLAN Status

You have to make sure that the wireless service is enabled in your computer before you proceed to the other troubleshooting options below as this error could occur for a simple reason as the wireless capability is turned off from your PC either on some built-in settings or physically. This is why you need to make sure that Wireless is enabled. And if it turns out that it is disabled, you need to turn it back on and then reconnect to the wireless network again. You should now be able to connect to the internet without any issue.

Option 2 – Try to check the WLAN AutoConfig Service

The WLAN AutoConfig service is the one that provides the logic and functionality required to discover, connect and configure wireless networks with your PC. Aside from that, it also contains the module that allows your PC to be discoverable to other systems on a network. Thus, you need to verify if the WLAN AutoConfig service is on or not.

• Tap the Win + R keys to open the Run dialog box.
• And in the field, type in “services.msc” and hit Enter to open Services.
• After opening the Services window, look for the entry named “WLAN AutoConfig” and then right-click on it and select Properties from the context menu.
• Next, click on the Start button to turn on the service and then set the startup type as “Automatic”.
• Then try to connect to your Wireless network again and check if the issue has been resolved.

Option 3 – Try to reset the Network Configurations

Resetting the Network Configurations can also help you in fixing the Windows Wireless service as the network settings often get disrupted or corrupted in a variety of different cases every now and then. Note that this module will reset all the network settings stored on your computer.

• Tap the Win + S keys to open Search and then type in “command prompt” in the field.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, copy and paste the following command and hit Enter to execute it:

netsh winsock reset

• The command given will reset the Winsock data. Once it is executed, restart your PC for the changes to take effect and then check if the internet connection is now fine.

Note: Do make sure that the WiFi drivers are up to date. To do that, follow these steps:

• 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. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. 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.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it.

Option 4 – Perform System Restore

Recently, a lot of issues have resurfaced after users installed the latest Windows update. So the wireless service issue might also be related to it. To fix the problem, you can perform System Restore to roll back your Windows to the last time when it was working just fine. It automatically creates backups in time whenever you install a new update or periodically. Follow the steps below to perform System Restore.

• Tap the Win + S keys to open Search and then type in “restore” in the field and select the topmost result.
• Once you’ve opened the restore settings, click on System Restore located at the beginning of the window under the System Protection tab.
• After that, a wizard will appear that will guide you through all the steps needed to restore the system. You can choose either the recommended restore point or a different one.
• After you select the restore point, click Next to proceed to the next on-screen instructions.
• Then select the restore point where the Windows Update was installed on your computer. If you have more than one restore point, you can just select the latest restore point and check the functionality from there. If it doesn’t work, you can just try another restore point.
• Another prompt will appear and will ask you to confirm your actions. Click OK and wait for the system to be restored. Once it’s done, check if the problem’s now fixed.

Nvidia announced the third generation of GeForce RTX GPUs called Ada Lovelace. New technology is bringing 76 billion transistors with 18,000 CUDA cores along with new gen ray tracing cores and improved Tensor cores as well. The new lineup also comes with DLSS 3 which is vastly improved from its previous version pushing a 4 times increase in frame rates over native rendering.

RTX 4090, a better model of GPU will come with 16,384 CUDA cores and a boost clock speed of 2.52 GHz. Also, it is packed with stunning 24 GB of GDDR6V VRAM. In Nvidia's words, its performance is twice faster than the 3090 Ti in games like Flight simulator, three times faster on Portal RTX, and four times faster on RacerX.

RTX 4080 comes in two modes, one with 12GB VRAM and a stronger one with 16GB VRAM but differences do not end here. The lower model is packing 7,680 CUDA cores while the stronger one is going to 9,728 CUDA cores. We will wait to see how will these cores count impact real-world performance in games.

As for prices, the flagship model RTX 4090 will be $1,600 USD and it will hit the market on October 12th. RTX 4080 12GB model will be $900 USD and the model with 16GB VRAM will go up to $1,200 USD. This, of course, is the price for Founders Edition cards, OEM cards from third parties like ASUS, MSI, Gigatech, etc will cost more.

HWiNFO (Hardware Information) is a professional hardware information and diagnostic tool supporting the latest components, industry technologies, and standards. It's targeted to recognize and extract the most possible amount of information about computer hardware which makes it suitable for users searching for driver updates, computer manufactures, system integrators, and technical experts too. Retrieved information is presented in a logical and easily understandable form and can be exported into various types of reports. System health monitoring and basic benchmarking available too. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

Getting errors while trying to update your Windows 10 computer is not an uncommon occurrence. Although some of them are easy to fix, there are others that need a lot of time and research in order to resolve. One of these tough Windows Update errors is Error 0x80244007. This kind of Windows Update error halts the process of Windows Update and a simple system restart won’t help much to fix it. When you encounter this Windows Update error, you will see a description that says, “SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_* error codes”. One of the main causes of such an error is that Windows was not able to renew the cookies for Windows Update. To fix this error, here are some suggestions that might be useful.

Option 1 – Clear up temporary or junk files

The error could be caused by some temporary or junk files in your computer and so you need to clear them up to fix the problem. You can achieve that using the Storage Sense feature.

• Open Setting > System > Storage from the WinX Menu.
• From there, you will see a list of all the local and connected storage devices along with the details on the free space. Make sure that Storage Sense is on.
• Next, find a link that says “Free Up Space” and click it to open.
• After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
  • Windows Upgrade Log Files
  • The system created Windows Error Reporting Files
  • Thumbnails
  • Temporary Internet Files
  • Previous Windows Installation Files
  • Delivery Optimisation Files
  • DirectX Shader Cache
• Choose the files you want to get rid of and then click on the remove files option. Note that you’ll have an idea of the total size as you select any of the junk files listed above.
• Now go to the “Free Up Space Now” section and click the Clear Now button. This will get rid of all the temporary or junk files in your computer and should hopefully fix the Windows Update error 0x80244007.

Option 2 – Try running the Windows Update troubleshooter

Windows 10 have various troubleshooters that can help you resolve many system issues. So if you’re dealing with Windows Update errors like Error 0x80244007, you can run the Windows Update troubleshooter to resolve it. 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 3 – Try to reset the Windows Update components

If by any chance that the second option didn’t work, resetting the Windows Update components could also help you resolve the problem. How? Refer to the following steps:

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below and don’t forget to hit Enter after you type one command after the other.
  • ren C:WindowsSoftwareDistribution SoftwareDistribution.old
  • ren C:WindowsSystem32catroot2 Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.