Hard drive shows wrong free space

One of the most common and bothersome issues with a printer is when it refuses to get configured or set up on your computer. Thus when your printer has some configuration issues, you will most likely encounter the error 0x00000709. This occurs if there is already a default printer set and configured or Windows does not want to configure the new printer at all. The operation could not be completed (error 0x00000709), Double check the printer name and make sure that the printer is connected to the network. Today, we will try two fixes that may help you get rid of this error.

Option 1 – Run the Printer Troubleshooter

One of the first basic troubleshooting you can perform to resolve the printer issue is running the Printer Troubleshooter. This built-in troubleshooter can detect and automatically fix the problem for you. To use it, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• Next, type “exe /id PrinterDiagnostic” in the field and click OK or hit Enter to open the Printer Troubleshooter.
• Then click the Next button and follow the next on-screen instructions to fix the issue with the printer.

Option 2 – Try to use some Registry tweaks to add the Printer

You might want to use some tweaks to add the Printer but before you proceed, make sure to create a System Restore Point so that if anything goes out of hand, you can always undo the changes you’ve made.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “Regedit” in the field and hit Enter to open the Registry Editor.
• When a UAC or User Account Control prompt appears, click Yes.
• Once you’ve opened the Registry Editor, go to the following key location:

HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWindows

• From there, double click on the file named “Device on the right side pane under the Windows folder.
• Now add the name of your printer in the Value Data field as you can see below and then click the OK button.

Note: As you can see on the image above, you must not change the “.winspool.Ne02:” part and only the first one which is the name of your printer.

• After that, you will get a message that says, “Cannot edit Device: Error writing the value’s new contents, simply click on OK again. You have to take note of the existing permissions before you proceed to the next step. Once you’ve added the Printer, make sure to reverse the changes you’ve made to the Permissions.
• Now right click on the Windows folder located on the left pane and click on Permission.
• Select Restricted under the Group or user names section.
• Then check the checkboxes for “Full Control”, “Read” and “Special Permissions” under the Permissions for RESTRICTED section.
• After that click the Apply button and then OK to save the changes made.
• Next, right-click on the file named “UserSelectdDefault” and select Rename to rename it to your printer’s name.
• Now restart your computer to successfully apply the changes made.
• After the printer is added, don’t forget to reverse the Permission changes you’ve made early on.

Option 3 – Try updating the Printer drivers

You might also want to try updating your printer drivers. All you have to do is locate the USB Composite Device. For complete details, follow the steps below.

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the USB Composite Device option and right-click on it, and select the Update Driver from the options.
• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: You also have the option to download the latest version of your Printer from the manufacturer’s website.

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.

Once a tedious and unfriendly task of installing fonts has been severely made easier and more user-friendly. As technology advances daily so do some tasks. One of these tasks which today look unnecessarily complicated is fonts installation in Windows. What was once complicated navigation to control panel with an administrative account, today is two-click with the mouse anywhere, well anywhere on your hard drive, but still a great improvement nonetheless. Ok, so you have found cool new font which you like very much and you are eager to try it out, but how do you install it in Windows so your other software can find it and use it? The task is incredibly easy, let's presume that you have downloaded desired font or fonts to your hard drive from the internet, they are nicely placed in a folder, all you have to do is select which one you would like to install, right-click on any one selected and click on install. That's it, that is all that you need to do. Now in order to remove fonts first, you will have to go to the folder which has all fonts installed in the system. The location of this folder is conveniently enough c:\Windows\Fonts. In there select all fonts that you would like to uninstall from the system and simply delete them, that's it.

Recently, a number of users reported an error in Google Chrome that says, “ERR_SOCKET_NOT_CONNECTED”. If you are one of these users, read on as this post will guide you in resolving this error. This kind of error in Chrome is kind of vague so it could be caused by a couple of factors like DNS server issues, Socket Pools, third-party plugins or extensions, and many more. Whatever the cause may be, there are several options you can check out to resolve the problem. You can try to flush the Socket Pool or change the DNS address or remove unwanted extensions or reset your Google Chrome browser.

Option 1 – Try to flush the Socket Pool

• Open Google Chrome and in the address bar, type “chrome://net-internals/”.
• After that, select Sockets on the left side panel.
• Next, select Flush socket pools from the right-side panel.
• And once it’s done, restart your Chrome browser and check if the “ERR_SOCKET_NOT_CONNECTED” is fixed or not.

Option 2 – Try to change the DNS Server

In this option, you can try changing your current DNS settings to the Google Public DNS as it could also help in fixing the “ERR_SOCKET_NOT_CONNECTED” error. To do so, follow the steps below.

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8.8” and “8.8.4.4” and click OK and exit.

Option 3 – Get rid of any conflicting browser extensions

• Open Chrome and press Alt + F keys.
• Go to More tools and click Extensions to look for any suspicious browser extensions or toolbars.
• Click the Recycle bin and select Remove.
• Restart Chrome and press Alt + F keys again.
• Proceed to On Startup and mark Open a specific page or set of pages.
• To check if the browser hijacker is still active, click Set pages, if it is active, overwrite the URL.

Option 4 – Try to reset Google Chrome

Before you proceed, make sure that the Chrome browser is not running anywhere in the background via Task Manager. Once you’ve made sure that it’s no longer running, refer to these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then type “%USERPROFILE%AppDataLocalGoogleChromeUser Data” in the field and tap Enter to open this location.
• From there, look for the Default folder and then tap the Shift + Delete button and if a confirmation prompt appears, click on Yes.
• After deleting the Default folder, open Google Chrome and click on the three vertical dots icon located in the top-right corner to open the menu.
• Next, click on Settings and scroll down and then click on Advanced to open the Advanced Settings.
• Then scroll down until you see the “Reset and clean up” section and click the “Restore Settings to their original defaults” option.
• After that, you will see a confirmation box and from there, click on the Reset settings button to reset your Google Chrome browser.

Corefoundation.dll Error - What is it?

Corefoundation.dll error is a DLL error code associated with Apple software such as iTunes, MobileMe, QuickTime and etc. To understand this error better, first you need to understand what corefoundation.dll file is. Corefoundation.dll is a Dynamic Link Library file that is used by Apple software products. This file is created by Apple computer Inc and is designed to help open up some of the media files that you might have on your PC. DLLs help promote modularization of code, efficient memory usage, code reuse and reduced disk space allowing the operating system and the programs to load and run faster and take less disk space on the computer.

Error Messages

This error pops on the screen when there is an issue related to Apple software products on your system. Corefoundation.dll error is displayed on the computer screen in any one of the following formats:

“The program can not start because corefoundation.dll is missing from your computer. Try reinstalling the program to fix this problem”. "This application has failed to start because CoreFoundation.dll was not found. Re-installing the application may fix this problem." “The procedure entry point_CFBundleCopyFileTypeForFileData could not be located in the dynamic link library corefoundation.dll.” "MobileMe Control Panel cannot continue as Apple Application Support is missing or outdated. Please uninstall and reinstall the latest version of iTunes and MobileMe Control Panel to fix this issue.”

Though this error code is not fatal but if it is not fixed immediately it will hamper your ability to load and run Apple programs on your system.

Solution

Error Causes

Corefoundation.dll error can be triggered due to several reasons. Here are some of the most common corefoundation.dll error causes:

• Outdated PC drivers
• Viral infection
• Damaged Windows registry files
• Corrupted corefoundation.dll file
• Missing corefoundation.dll file
• Incorrectly installed third-party software

Further Information and Manual Repair

To fix this issue on your computer here are some of the best, easy and quick do it yourself methods that you can try:

Method 1: Download the Original Corefoundation.dll File

If the underlying reason for corefoundation.dll error is file corruption or it goes missing, then the best way to resolve is to download the original corefoundation.dll file. Once you download it, paste it to its exact location. DLL files are normally located in the following location C:\Windows\System32. Once you paste it, register the file by typing ‘regsvr corefoundation.dll’ at the command prompt. When the process is complete, restart your PC to activate changes. Alternatively, you can uninstall and re-install any Apple Software you may have on your Windows Computer. To do that, Open the Control Panel, navigate to "Install/Uninstall a Program", search for Apple software, and uninstall them.

Method 2: Update Window Drivers

If the error code is related to outdated drivers, then it is recommended that you update them promptly to resolve the corefoundation.dll error on your PC. This can be done by using a driver update wizard from within Device Manager. The driver update wizard walks you through the entire drive update process, making updating a hassle-free process.

Method 3: Download Restoro

If the error still persists, then try method 3. Sometimes the cause of corefoundation.dll can be viral infection or registry issues.  Viruses may enter your PC unknowingly through phishing emails and downloads which can corrupt and damage your dll files. Also, if you don’t clean your registry frequently, unnecessary and obsolete files may accumulate in the registry like cookies, junk files, internet history and temporary files. These files take up a lot of disk space corrupt DLL files and lead to disk fragmentation. Regardless of what the issue is, Restoro is your one-stop PC Fixer. It is a multi-functional and user-friendly repair tool embedded with 6 different scanners including a registry cleaner and an antivirus. It scans and removes all types of viruses and cleans and restores the registry too. Click here to download Restoro and resolve the corefoundation.dll error today!

Even with the new Groove Music in Windows 10, a lot of users still prefer to use the old Windows Media Player. This isn’t surprising since Windows Media Player still remains to be one of the best players you can find. However, that does not mean that it is without flaws as it could still encounter some issues from time to time. One of the issues you might encounter when using the Windows Media Player is when you try to burn DVDs or CDs but end up failing due to an error that pops up that says, Windows Media Player cannot detect the length of the file. At the time of writing, it isn’t clear yet what the real cause of the error is. However, there are several fixes that are provided in this post for you to check out so you can resolve the problem. You can try to get rid of any unsupported files from the burning list or you could also try running the Windows Media Player troubleshooters. Aside from that, you could also try to drag and drop music or change the burning speed. For more details, refer to the following options.

Option 1 – Get rid of the unsupported files from the burning list

You must get rid of the unsupported files from the list of files to burn. This list can be found on the right-hand side of the Windows Media Player. One of the indications that a file is causing problems is when there is a white cross in a red circle next to the file. You can simply click on that icon to remove the file from the burning list. Once you’ve gotten rid of all the unsupported files, try to burn your files to the CD or disk once more.

Option 2 – Try running the Windows Media Player troubleshooters

The next thing you can do to fix the error is to run the built-in troubleshooters for the Windows Media Player. Windows 10 actually comes pre-packed with three troubleshooters designed for Windows Media Player. They can help in fixing the “Windows Media Player cannot detect the length of the file” error. To run these troubleshooters, simply tap the Win + R keys to open the Run dialog box and type “msdt.exe -id WindowsMediaPlayerConfigurationDiagnostic” for the Windows Media Player Settings troubleshooter or type “msdt.exe -id WindowsMediaPlayerLibraryDiagnostic” for the Windows Media Player Library troubleshooter, or type “msdt.exe -id WindowsMediaPlayerDVDDiagnostic” for the Windows Media Player DVD troubleshooter.

Option 3 – Try to drag and drop music

Another thing you can check out is to drag and drop all the tracks into the Windows Media Player before you burn them. All you have to do is open the folder where the tracks are located and highlight all of them and then drag them to the Windows Media Player. It should now be able to detect the length of each one of the tracks without any errors.

Option 4 – Try to change the burning speed

Since the burning speed is set to fastest by default, you can try to change the burning speed to resolve the problem. Just open the Options window and then go to the Burn tab. From there, select either Medium or Slow burning speed and save the changes made. Now try to burn your files to the CD or disk once again.

Manually cleaning your PC registry may be the worst or best thing you ever decide to do. Registry keys that lie around on your computer, unused, can cause your computer to lag. This can end up in your computer not being able to load the easiest of programs and being slow at loading anything, let alone something that would take up a decent amount of memory. If your computer has slowed to almost an absolute stop, it is most probably the registry’s fault and the only option then is to clean it. You can get programs to do this for you, but they can be riddled with inaccuracies and viruses that could harm your computer even more. This is why some people choose to manually edit their computer. However, this is not without its flaws.

Registry Keys

Registry keys tend to have really long names. These names will be full of numbers and hyphens and will most likely give you no indication of what they do. Even some computer experts find it hard to understand what every computer’s registry keys do. This can make it very hard to see which ones are causing the problem; and if you don’t know what’s causing the problem, then there is no way you will be able to fix it. Some registry keys will be completely menial in what they do but some could be vital to even allow Windows to work on your computer.

Manual Registry Repair

Registry keys can also cause huge problems if you manually delete the wrong one. A lot of registry cleaners have the option to revive a key that they have deleted on you, which means that fixing an error that they made would be easy enough to do. However, when you manually delete registry keys, it will be an awful lot harder to get them back to work again afterward. This can cause your computer many problems and if you delete even one wrong key it is possible your computer will not even start. With the horrid naming system they have as well, it makes it very hard to determine what is important and what is not, which means it is all too likely that you will delete something important. However, those are the risks you have to take when you are cleaning out your registry. A registry cleaner has the same likelihood of messing with your computer and deleting something wrong that you have, so it is the same either way however a registry cleaner will do it with less hassle. But, some people say that if you do it yourself, it’s more likely to be right; that is why they prefer to do it manually and that is alright.

Conclusion

So, if you are manually deleting your registry keys that are unused, you’ll have to use a program that comes with Windows known as ‘regedit.exe’ which is incredibly difficult to use but may just be worth the hassle in the end. So, you don’t really need to put up with a slow computer, but be careful when messing with your registry manually! To repair and resolve this and other PC-related issues Click Here to download Restoro.

One of the great remote assistance software that helps you remotely access and control computers is TeamViewer. However, despite how efficient it is, there are still times when it throws up some errors and one of them is when TeamViewer is not able to connect and throws an error that says, “No connection to partner, Partner did not connect to router, Error Code WaitforConnectFailed”. This kind of error in TeamViewer mostly occurs when the Partner computer is not connected to a network. On the other hand, it could also occur when they are connected to a network so there are various causes for this issue. It could also be that the installation of the program itself was at fault or there is an incompatibility between the TeamViewer versions installed on both the computers and so on. Although there are several causes for this error, the potential fixes are still the same. You can try to restart the network or allow Full Access Control to TeamViewer or flush the DNS cache. For more information, refer to the following options but before you proceed, make sure that both your Windows 10 computer and TeamViewer program are updated to their latest stable versions.

Option 1 – Reboot your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Allow Full Access Control to TeamViewer

• First, open TeamViewer, and then from the Menu bar, click on Extras.
• After that, click on Options and select Advanced from the left side navigation panel.
• Next, click on the “Show advanced options” button located on the right-hand side.
• Then select Full Access from the drop-down menu of the Access Control option under the “Advanced settings for connection to this computer section”.
• Now click OK and check if the error is now fixed or not.

Option 3 – Try to flush the DNS configuration

You could also try to flush the DNS configuration in your computer to fix the error. How? Refer to these steps:

• Tap the Win + X key combination and click on the Command Prompt (Admin) option or you could also search “cmd” in the Cortana search box and right-click on Command Prompt from the search results and select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, enter each one of the commands given below sequentially in order to flush the DNS cache.
  • ipconfig/release
  • ipconfig/renew
  • ipconfig/flushdns
• Now type the exit command to close Command Prompt and then restart your computer and see if the problem is fixed.

On the other hand, you could also try to reset Winsock as well as the TCP/IP.

Option 4 – Run 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 5 – Try to perform Network Reset

You might perform a Network Reset to resolve the problem if none of the four given options worked. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

As you know, installing Windows 10 is quite a complicated process in the background even though it may look like an easy task in the foreground. There are times when the setup is stuck on the “Hi there” screen where you won’t be able to input any information in the fields given and you wouldn’t be able to do anything else since the screen does not move ahead. There are a lot of possible reasons why this issue occurs. It could be due to a damaged setup image, invalid boot configuration, and many more. To resolve this problem, there are several options you can check out. You can try to get a new setup image or run the Automatic Repair or you could also try to recreate the Boot Configuration files or BCD. To get started in checking out these solutions, make sure to follow the instructions provided below.

Option 1 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.

• You can start by creating and booting from a bootable Windows 10 USB Stick.
• After that, click on Repair your computer located on the bottom left corner when you are on the initial Windows Startup screen.
• Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
• Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

Option 2 – Try to rebuild the BCD files

You can also try rebuilding the BCD files to resolve stuck screen issue in your Windows 10 computer.

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
  • bootrec /FixMbr
  • bootrec /FixBoot
  • bootrec /ScanOS
  • bootrec /RebuildBcd
• Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.

Option 3 – Try recreating the Windows 10 installation USB

Recreating the Windows 10 installation USB might help in fixing the problem. You can use a USB drive to do so but make sure that it has a great read-write speed. Follow the steps below to recreate Windows 10 installation USB”

• Click this link and then click the Download Tool Now button.
• Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
• Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option 4 – Try getting a new Windows image file

If none of the four given options above worked, you might want to get a newer installation image using the Windows Media Creation tool. After that, create the bootable USB drive and once completed and then try to run the Windows 10 setup again.

0x800ccc79 Error - What is it?

0x800ccc79 error is an error message that you may come across when sending emails through Outlook Express from Microsoft. This error message is accompanied by a notification that is displayed as ‘email was not delivered’ or ‘the server doesn’t support SSL connection’.

Solution

Download Available to Recover all Lost Outlook data

Error Causes

This error code 0x900ccc79 is triggered due to the following causes:

• Problems related to email servers
• Changes in the configuration settings
• Corrupted Windows Registry

Further Information and Manual Repair

When you receive the error 0x800ccc79 it may hamper your ability to send emails. Therefore it is advisable to fix it to ensure your emails are sent and received without any difficulty.

This Outlook error 0x800ccc79 is quite easy to repair. By following the quick fix 0x800ccc79 error code solutions given below you can resolve this error in just a couple of minutes.

Here’s what you need to do to fix this error right away:

Cause: Configuration issues

Solution: If the error occurs due to Outlook Express being configured to use the SSL protocol while sending and receiving emails via the web, then to resolve it, you need to allow Outlook Express to bypass the Secure Socket Layer settings.

To do so, click on ‘tools’ and then on ‘Accounts’. Now select the email account that you want to modify.

Now select the ‘Properties’ tab and then click on ‘Advanced Settings’.

Here search for the following text message ‘This server requires a secure connection’. Once you locate it, uncheck all the checkboxes given next to this option. After that save the changes and restart Outlook Express to see bring the changes into effect.

Cause: Missing or Corrupt Registry Entries

Solution: If the error 0x800ccc79 occurs due to missing or corrupt registry entries, then the best way to fix this error is to download and install a good registry cleaner on your PC.

The registry cleaner will help you clean your corrupt and damaged Windows registry entries and get rid of this error right away. It is suggested you download the registry cleaner tool from a reliable website to avoid any malware or virus downloads simultaneously.

Once you download the registry cleaner on your system, click on scan. The cleaner will scan your computer completely for registry errors and show you the results in a list form.

After the scanning is complete, click on repair to fix the errors.

So, next time, if you or anyone at your office comes across the Outlook Express error 0x800ccc79, you can try these solutions and fix the error immediately without waiting for the network personnel to come and resolve it.