Fix Device not migrated on Windows 10

Microsoft starting as of today will block its Office 365 users if they are using Internet Explorer or early versions of Edge browsers. So if you are using older non Chromium Edge versions of Microsoft browsers you can no longer access Office services until you switch. Now normally I would fully support this kind of decision since Internet explorer is a slow and vulnerable browser and the edge is similar in that regard. The new edge browser is great and it should be used but the issue I have is that Office 365 is not free, it is a premium feature and I am wondering how Microsoft plans to deal with people that have already paid for service but suddenly cannot access it anymore.

Error code 0x8007007b - What is it?

Error code 0x8007007b will present itself when Windows users are trying to activate Windows. You may try to activate it through the update and security option, but it is likely that you will receive the same error code. Error code 0x8007007b may be presented when Windows 7 and Windows 8.1 users try to upgrade and activate Windows 10 on their computer.

Common symptoms include:

• An error message will display that says Windows cannot be activated. The KMS host cannot be located in the DNS, please have the system administrator verify that the KMS is published correctly in DNS.
• Error 0x8007007b will be displayed, stating that the file or directory name or the volume label syntax is not correct.

Solution

Error Causes

There are multiple causes for the user to see this error code, including if a user is using volume-licensed media while installing a number of various Windows operating systems. This error may also be caused because the activation wizard cannot connect to a KMS host computer. It is likely that if the user has a volume-licensed form of media, they were likely given a MAK (multiple activation keys).

Further Information and Manual Repair

There are several ways to go about repairing error code 0x8007007b. It is important to try all of the methods, but if it is too difficult or you do not know what you are doing, please do contact a Windows repair technician. They will likely be able to fix the problem with ease.

Method One: Instead of KMS activation, use a Multiple Key Activation

When KMS activation is not used, and when there is not a KMS server, the product key type should then be changed to a MAK. For MSDN (Microsoft Developer Network) or TechNet, the SKUs that are listed on the media are generally volume-licensed media, and that means that the product key that is supplied is a Multiple Activation Key.

To change the KMS to a MAK, click Start, All Programs, Accessories, and then right-click on Command Prompt. Click Run as Administrator. If prompted for a password or confirmation, enter it now.

When the command prompt opens, type in the following command, and press enter after:

slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx (these x's are representative of the MAK product key).

Method Two

While on the desktop, press the Windows key and R. The Run window should appear, and then you should enter the following command: Slui 3. Press Enter and then wait for the window to appear. This window will ask for the operating system activation product key. Enter the product key and then press the Activate button. Reboot the computer. Now the Error Code 0x8007007b should be gone.

Method Three

Open the Command Prompt with access as administrator as mentioned previously. Enter the following command: sfc /scannow. The command will then complete its task. This will take a good bit of time, so leave the computer to do its work. The sfc must finish the scan. When the scan has finished, reboot the computer. Now you can check for activation. The error code should be gone.

Method Four: When the client can't locate a KMS host on the network to complete activation

This method for correction should be used when the network does have a KMS host computer setup, and the client is not able to locate the KMS host on the network to complete activation.

To verify that the computer does in fact have the KMS host installed. Click Start, All Programs, Accessories, and then right-click on Command Prompt. Run as administrator. If you are now prompted to enter a password or confirmation, do so. When the command prompt box comes up, type in the following command, and then press Enter: nxlookup -type=all_vlmcs._tcp>kms.txt

The command will generate a file, open this KMS file. The file will contain one or more entries. As a default, the KMS host server will dynamically register a DNS SRV server evidence once every 24 hours. In order to check the registry to ensure that this is happening, follow these steps:

• Click Start, type in regedit, and then press Enter.
• Locate the key HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSL and then click on it.
• The DisableDnsPublishing subkey should be present and have a value of 1. If it is missing, create a DWORD value by right clicking DisableDnsPublishing, click Modify, in the Value Data box type in 0, and then click Okay.

Method Five: Use An Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

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.

The network driver error is a not serious Windows issue.  It happens from time to time and luckily it can be solved with a little effort and in a short time period. Today in this article we will explore the most common solutions for driver malfunction for Network adapter inside Windows 10. If you have this particular problem, go from step 1 to the last step since all steps are meant to go from simplest to the most complex. All of that being said let us fix your Network driver issue.

1. Check to see if the cable is plugged in and not malfunctioned

   The first common issue of the network now working can be cable malfunction or bad contact in your network adapter or in HUB/SWITCH. There are various tools to check the quality and working order of cable but you could also make sure that it is not a cable issue by trying connection with the correct working cable. If the network is restored with another cable then change the malfunctioning cable and your issue is resolved if the problem persists move to the next step.

2. Check if Windows troubleshooter will resolve the issue

   Righ-click on the network icon in the taskbar and choose to troubleshoot problems. Windows built-in tools could resolve issues and fix them for you. If by any chance Windows is not able to find or resolve issues move to the next step.

3. Check if the Device Manager is reporting an error and update the driver

   If the hardware is functioning properly then the issue might be in Windows not detecting device or driver malfunction. In any case, the Device Manager will be the one who will report this problem. In order to check to see if the driver is properly working press ⊞ WINDOWS + X to open the hidden start menu. Once it opens, click on Device Manager to open it, If you have a driver device error inside Windows, you should see it immediately when entering the Device Manager, it will have a yellow exclamation mark beside it. Right-click on it and choose update driver.

4. Reinstall driver

   If driver update failed or you already have the latest drivers, reinstalling them could fix the issue since drivers might have corrupted during installation of some update or application. Follow steps from point 3 to get to the driver in Device Manager, then right-click on it but instead of update choose to uninstall. Reboot Windows once the driver is uninstalled and Windows will install a new one automatically. If you do not want to update drivers automatically, do not restart your system, instead install the latest driver for your device, then reboot. Since this is a network error, you will have to get drivers on another computer and transfer them via USB to malfunctioning one.

5. Check Windows update

   Check to see if the latest Windows update is installed, update your Windows if needed

6. Fix driver issue with DRIVERFIX

   If everything else fails, get DRIVERFIX, a premium solution for your PC issues, and fix driver errors.

A runtime error is commonly an error that's created after the PC is operating software and encounters a problem of some form. For instance, a runtime error like run-time error code 7 reveals an "out of memory" dilemma.

Solution

Error Cause

Run-time errors are normally brought on by clashes with TSR (Terminate and Stay Resident) applications or additional operating applications, software problems, storage problems, or pc viruses.

Troubleshooting a Run-time Error

First, enter the run-time error signal into a search engine to see what info you will get about the precise runtime issue you are receiving. Next, end - job all running applications and TSRs to make sure these aren't the origin of the issue. You can certainly do so by obtaining the job manager by striking Control Alt Delete.

In case your issue is regularly occurring with a unique program, go to that system programmer's site and obtain any upgrades and patches. If unavailable, try uninstalling the application involved and reinstalling it.

In the event the issue is occurring with the os, you may consider reinstalling it although it is a huge commitment. A much better idea would be to try a fix for both Windows XP or Windows 2,000. It is possible to fix and scan files by typing : sfc / scannow, heading to the Begin switch, Run, and then pushing enter. Make certain to put an area between sfc and the reduce.

You might have an equipment or storage dilemma if these measures have not resolved your run-time errors. If that is the situation, contact the support of the application under consideration for potential support accompanied by the pc or motherboard manufacturer.

Many run-time problems can be solved by upgrading the application that's creating the problem. This is only because the programmer's frequently releasing patches and improvements for their applications as insects are found and repaired.

Storage problems may frequently be fixed by rebooting the pc. Consider a reboot a short-term repair. Rebooting clears the memory but in case your COMPUTER does not have adequate memory for your applications you're operating, or sufficient hard-drive space you'll immediately run out of memory again. Something less than this sum may cause memory issues since the computer's swap file isn't in a position to expand in dimension as required.

To assess the quantity of free area, available My Computer and right-click on the HDD, generally the D: drive. Select Attributes in the menu and see the disc's ability. Perform the disk clean-up function by following prompts and pressing the Disk Clean-up button, if the room is reduced.

You may be getting run-time errors, in case your storage chip is really failing. Eliminating and changing the awful memory chip will solve the difficulty. If you're encountering other runtime-related errors, like an install runtime issue, try cleaning away the portions of the registry with some software solution. 

Bttray.exe Application – What is it?

Bttray.exe is basically a Bluetooth Tray Application. Bluetooth Tray Application is developed by WIDCOMM. It provides a system tray icon that allows users to see the status of their Bluetooth connections at a glance. It allows you to easily access the configuration and settings for the Bluetooth products enabling you to change the configuration of the Bluetooth devices. The bttray.exe application error may pop up on your computer screen due to some issue with the Bluetooth software. The process fails to initialize and therefore stops working. Bttray.exe application error code is  displayed in the following format:

• “BTTray.exe can’t initialize (0xc0150004).”
• “BTTray.exe – System Error”

Though this is not a fatal or critical computer error it is advisable to resolve it otherwise it will hamper your access to Bluetooth software and cause you a great deal of inconvenience.

Solution

Error Causes

Bttray.exe application error code may be triggered due to one of the reasons stated below:

• Bttray.exe application is damaged
• Bttray.exe is accidentally removed from your PC
• The Bluetooth software or driver becomes problematic.
• Some modules that run by the process are corrupt
• Malware infection
• Invalid registry entries

Further Information and Manual Repair

If you experience a bttray.exe application error code on your system, it is recommended to fix it right away. To resolve this error you don’t have to be a computer programmer or a technical whiz or have to hire a professional and spend hundreds of dollars in repair. It is easy to fix, simply follow the manual methods given below:

Method 1- Reinstall Bluetooth Software

If the Bluetooth Software is damaged or outdated, the bttray.exe will also not work. If this is the cause of the error code, then simply reinstall Bluetooth software on your system. To do this, first, uninstall the current software and then download the latest version of the Bluetooth Software on your PC. To uninstall click start, go to the control panel, and then programs. Now select Bluetooth software and click uninstall to remove it. After that, install the latest version and update it. To activate changes

Method 2: Scan for Malware

Sometimes the bttray.exe application error code may pop up due to malware and viral infection. To fix it, download a powerful antivirus. Scan and remove malware to resolve.

Method 3: Clean Registry

The registry basically saves all the activities being performed on the PC including junk and obsolete files. If the registry is not clean frequently, unnecessary files like cookies, junk files, temporary files, and internet history can take up a lot of space and cause the registry to damage. Due to this error code like the bttray.exe application can also pop up. To resolve, clean the registry. You can do it manually but that may be difficult and time-consuming if you are not a computer programmer. However, a good alternative would be to download Restoro. This is a user-friendly and next-generation PC Fixer deployed with multiple utilities like a registry cleaner and an antivirus. Simply run it to remove viruses and clean the registry. Click here to download Restoro and resolve the bttray.exe application error now!

There are instances when instead of fixing problems the Windows Update brings you problems on your Windows 10 computer. You might even see some pending Windows Updates which for some reason, refuse to install no matter what you do. The good thing is you won’t have to deal with those failed and pending updates that are incompletely downloaded to your PC as you can actually delete them. Follow the instructions prepared below to delete the failed and pending Windows Updates.

Step 1: The first thing you have to do is delete all the contents in the Temporary folder

• Tap the Win + R keys to open the Run dialog box.
• Next, type in “%temp%” in the field and hit Enter or click OK to open the Temporary folder.
• From there, select all the folders and files within the Temporary folder and then delete them all.

Note: %temp% is one of the many environment variables in Windows that could open the designated folder by Windows as the Temporary folder which is usually located at C:\Users[username]AppDataLocalTemp.

Step 2: Next, remove the pending.xml file

• Go to the C:\Windows WinSxS folder.
• Once you’ve opened the folder, look for a file named “pending.xml” file and right-click on it and you can either rename it or delete it.
• After that, the Windows Update should delete the pending tasks and build a fresh new update.

Step 3: Delete all the contents of the SoftwareDistribution folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

• 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, got to the C:\Windows\Software\Distribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Step 4: Try resetting the catroot2 folder

You can also try resetting the catroort2 folder as it is known to fix tons of Windows Update issues. Both the Catroot and catroot2 are Windows operating system folders that are required for the Windows update process.  So when you run the Windows Update, the catroort2 folders stores the signatures of the Windows Update package and helps it in the installation. It makes use of the “%windir%System32catroot2edb.log” file in the updating process. Afterward, the updates are stored in the SoftwareDistribution folder which is used then by the Automatic Updates in order to execute the updating process. Keep in mind that you must not rename or delete the Catroot folder. Although the Catroot2 folder is recreated automatically by Windows, the Catroot folder isn’t.

One of the most sophisticated Artificial Intelligence or AI assistants there is in the market is Cortana. However, no matter how sophisticated this AI assistant may be, there are still times when you encounter issues with it. So if your Cortana is not connecting to the internet, worry not for this post will guide you in fixing the problem. This connection issue in Cortana might have something to do with the settings, network connectivity, or your Microsoft account. In addition, it could also be that the Firewall or antivirus program interferes with its connection. Whichever the case is, here are some possible solutions that could help you resolve the problem.

Option 1 – Try to power cycle the modem, router, and computer

• Connect the modem, router, and the PC hard-wired and then switch all of these three devices off.
• Turn on the modem and wait for 30 seconds.
• Turn on the router and wait for 30 seconds as well.
• Finally, turn on the computer and check if you can now successfully connect to the internet.

Option 2 – Check if your router or ISP is properly working

Since the basis for this issue is that Cortana is not connecting to the internet even though you are able to access websites using your browser, you might want to check your router or ISP (Internet Service Provider) and see if they’re functioning properly.

Option 3 – Try changing your internet connection

You can also try changing your internet connection and see if it fixes the problem. If you are using Ethernet, you can try connecting to a Wi-Fi connection and see if Cortana is able to connect or not.

Option 4 – Try to run the Search and Indexing troubleshooter

You might also want 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. Note: You can also run the Network Troubleshooter as it can also help in resolving the issue especially if the problem is in the network.

Option 5 – Try to remove Proxy

Removing the Proxy might also help you in fixing the connection issue in Cortana. Here’s how you can do it:

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 6 – Verify your Microsoft account

In some cases, Cortana might not be able to connect to the internet because your Microsoft account is no longer verified. This usually happens when you use a two-step authentication system with your Microsoft account. To verify it, just open Settings and click on Accounts. After that, check if you have a Verify hyperlink under your Microsoft account or not then click on Verify. Afterward, follow the next on-screen prompts to verify your Microsoft account. Once your account is verified, restart your computer.

Option 7 – 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 8 – Try to reinstall Cortana

If none of the options given above works, you must consider reinstalling Cortana.

• First, right-click on the Start button and click on the Windows Powershell (Admin) option from the list.
• Next, 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 Cortana is now able to connect.

There are times when you suddenly encounter a Blue Screen error like DRIVER_POWER_STATE_FAILURE error when resuming from Sleep or right after you shut down or restart as well as switch from Hibernate mode. This kind of Blue Screen error is due to some issue with the driver state. Moreover, the bug check “0x0000009F” in the error also indicates that a driver is in an inconsistent or invalid power state. The DRIVER POWER STATE FAILURE Blue Screen error usually occurs during events that involve power state transitions like shutting down, moving in or out of standby mode, or hibernate mode. To resolve this error, you can check out the suggestions given below.

Option 1 – Update the Device drivers

The device driver installed in your computer might be incompatible with your operating system which is the reason why the DRIVER POWER STATE FAILURE Blue Screen error occurs. To fix that, you have to update your device drivers.

• Reboot your computer into Safe Mode with networking support.
• Tap the Win + R keys on your keyboard to open the Run dialog box.
• After that, type “msc” in the field and hit Enter or click OK to open the Device Manager.
• After opening the Device Manager, update all the outdated Device drivers on your computer.
• Next, right-click on all the driver entries that are appropriately labeled, and then click the Update driver option.
• Now restart your PC and check if the BSOD error is fixed or not.

Option 2 – Uninstall any faulty device drivers

• Tap the Win + R keys on your keyboard to open the Run dialog box.
• After that, type “msc” in the field and hit Enter or click OK to open the Device Manager.
• From there, look for any device driver which has a yellow exclamation mark which indicates that something is wrong with them.
• And then right-click on each one of them and click on Uninstall.
• Once you’re done uninstalling the faulty drivers, restart your computer and allow your computer to reinstall the drivers you just uninstalled.

Option 3 – 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 rtwlane.sys Blue Screen error. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 4 – Try to remove external hardware

If there is any external hardware plugged into your computer especially the new ones, you can try removing it and then check if the Blue Screen error persists. If the problem gets solved, you might want to update the driver of that particular hardware. On the other hand, if you’re still getting the error, then proceed to the next given options below.

Option 5 – Try resetting Windows 10

To fix this BSOD error, you can try resetting Windows 10. Doing so won’t get rid of any file in your system – instead of erasing all your media files and documents, this reset option resets all the system settings and files.

Option 6 – Try running the System File Checker Scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the DRIVER POWER STATE FAILURE Blue Screen error. SFC is a built-in command utility that helps in restoring corrupted files as well as 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.