Fix the MEMORY 0x000000FC Stop Error

If you’re suddenly unable to launch or open Google Chrome or unable to load web pages, then it’s most likely that the files in Chrome have been corrupted or some plugin is taking up a lot of resources which is why you encounter an error message saying, “Google Chrome has stopped working”. And when you try to check the Task Manager, you’ll see that Chrome is really taking up lots of resources, however, when you check the Taskbar, strangely, you will see nothing. If you are currently facing this issue in Chrome on your Windows 10 PC, follow the given options below.

Option 1 – Kill Google Chrome’s process in the Task Manager

If you aren’t able to open Chrome, then maybe its process is running in the background and you don’t see the browser windows. If that’s the case, you may have to force quit the browser and then try to open it again.

• First, right-click on the Taskbar then select the Task Manager. And if the Task Manager is not responding, you can just use the Alt + Ctrl + Del keys and then select the Task Manager.
• After opening the Task Manager, under Processes, look for Google Chrome’s process which would most likely be named “chrome.exe”.
• Right-click on Google Chrome’s process and then select the End task option.
• Now try to open Google Chrome again.

Option 2 – Try checking if your antivirus program is blocking Google Chrome

There are instances when due to false-positive, a security or antivirus program might block Chrome which is why it failed to open properly. Thus, you can just disable the security program temporarily and then check if you can now open Chrome or not.

Option 3 – Delete the User Profile in Chrome

You can also try deleting the User Profile folder in Chrome. To do so, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then copy and paste “%USERPROFILE%AppDataLocalGoogleChromeUser Data” and hit Enter.
• From there, look for a folder named “Default folder” and then copy the folder to another drive as a backup.
• After creating a copy of the folder, delete the Default folder.
• Next, open Google Chrome again and go to Settings > Advanced > Reset.

Option 4 – Disable the Extensions in Chrome

There are instances when issues on a browser are triggered or caused by some problematic extension. To find out which one of your extensions is causing the problem, disable them all first and then enable them back one by one.

• Click on the three-dotted icon for the menu located at the top-right corner of your screen.
• Then click on the More tools option and go to Extensions.
• From there, you will see a list of all the installed extensions in Chrome.
• Disable all these extensions and restart the browser.
• Now enable them back one by one to figure out which one of them is the culprit. You could also remove extensions that you no longer use.

Option 5 – Run the Chrome Cleanup tool

You might also want to try running the Malware Scanner & Cleanup tool in Chrome. This is a built-in tool that can help you get rid of any unwanted pop-ups, banners, ads, unusual startup pages, toolbars, and malware. Thus, it can help you to resolve the issue in Chrome.

Option 6 – Try to reinstall Chrome

If running the Malware Scanner & Cleanup tool in Chrome didn’t work out for you, you can try reinstalling it. To do so, follow these steps:

• Open the Settings app and go to System > Apps & features.
• From there, look for Chrome and uninstall it from your PC.
• Then go to the official website of Google Chrome and download its latest version and install it.

In this post, you will be guided on how you can turn on or turn off the Tailored Experiences feature in Windows 10 using three methods – via Settings, Registry Editor, and Group Policy Editor. The Tailored Experiences feature in Windows 10 helps Microsoft in delivering recommendations about Microsoft Products. The diagnostic data that comes with it allows Microsoft to know about its consumers’ experiences as well as collect feedback. To simply put it, tailored experiences are personalized tips, ads, and recommendations that enhance Microsoft products and services for consumer needs. And when you enable this feature, Windows will collect information from your browser, apps, features, and many more. After collecting information, it will offer contents that are tailored based on the data gathered on the lock screen of your computer, Windows tips, and other related functions. On the other hand, the diagnostic data is the one that allows Microsoft to get feedback from the customer. So if you’ve noticed some prompts when you use Windows that ask you about the experience, that’s actually a part of the diagnostic data. A lot of users find this feature useful. However, there are also skeptical ones that don’t share the same sentiments. If you are one of the skeptical ones, you actually have the option to turn this feature off if you do not want Microsoft to show ads, recommendations, and so on. It is also recommended that you enable the Diagnostic Data collection as you can choose to delete any collected data, as well as control the feedback frequency from Automatic to Once a day, or once a week, or to never. As mentioned, there are three methods you can choose from to either turn on or turn off Tailored Experiences. You can do it via Settings, Registry Editor, and the Group Policy Editor. To get started, follow the options provided below.

Option 1 – via Settings

To turn on or off Tailored Experiences using Settings, refer to these steps:

• Go to Settings and here, click on Privacy.
• Next, go to Diagnostic and Feedback.
• From there, toggle off the control under the Tailored experiences option to turn it off or toggle it on, if you want to turn it on.

Option 2 – via Registry Editor

To turn on or off Tailored Experiences via Registry Editor, follow the steps below.

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and then tap Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionPrivacy
• After that, look for the DWORD named “TailoredExperiencesWithDiagnosticDataEnabled” and change its value to 0 if you want to turn it off or 1 if you want to turn it on.

Option 3 – via Group Policy Editor

To turn on or off Tailored Experiences using the Group Policy Editor, here’s what you have to do:

• Tap the Win + R keys to open the Run prompt and type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to this policy setting: User ConfigurationAdminstrative TemplatesWindows ComponentsCloud Content
• Here, double click on the “Do not use diagnostic data for tailored experiences” option and select Enabled. Once you do that, you will see the following description:

“This policy setting lets you prevent Windows from using diagnostic data to provide tailored experiences to the user. If you enable this policy setting, Windows will not use diagnostic data from this device (this data may include browser, app, and feature usage, depending on the “diagnostic data” setting value) to customize the content shown on the lock screen, Windows tips, Microsoft consumer features, and other related features. If these features are enabled, users will still see recommendations, tips, and offers, but they may be less relevant. If you disable or do not configure this policy setting, Microsoft will use diagnostic data to provide personalized recommendations, tips, and offers to tailor Windows for the user’s needs and make it work better for them. This setting does not control Cortana tailored experiences, since there are separate policies to configure it.”

If you are trying to connect to the internet using a Wi-Fi, Ethernet, or a Wi-Fi connection and you suddenly encounter Error 633, then read on as this post will guide you on how you can fix this problem in your Windows 10 computer. According to users who encountered the same problem, when they try to connect to the internet, an error pops up that states, “The modem or other connecting device is either already in use or not appropriately configured”. This error is the VPN Error 633 which indicates that the modem is malfunctioning due to some broken configuration. It is possible that this broken configuration is caused by the WAN Miniport device which is associated with your preferred VPN protocol. It could also be due to the TCP port that’s required for the VPN connection to work might be used by another application. There are instances when Error 622 could occur when there are multiple internet connections set up on one device or when the communication port is exploited by another program. It could also occur when the affected modem is not bound to one specific device. Thus, any model and computer can be affected by this problem. The first and basic thing you can do to fix the VPN Error 633 is to turn off or unplug the modem your computer is using and then plug it back in to see if the problem is fixed. If not, then there are several other potential fixes you need to check out to resolve the problem. You can try the suggestions provided below and see if any of them help.

Option 1 – Run the Network Adapter Troubleshooter

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

Option 2 – Try to explicitly reserve the TCP port

The next thing you can do to fix the error is to reserve the TCP port explicitly and to do that, follow the steps below.

• Tap the Win + R keys to pull up the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters
• After that, follow the path New > Multi-String Value on the edit menu and rename the multi-string value as “ReservedPorts” and then double click on it.
• Now in the value data of ReservedPorts, input “1723-1723” and click OK to save the changes made.
• Close the Registry Editor and restart your PC. Once your computer has restarted, check if the VPN Error 633 is fixed or not.

Option 3 – Try to use the netstat command

• In the Windows Start Search, type “cmd” and from the search results that appear, right-click on Command Prompt and then select the “Run as administrator” option.
• After opening Command Prompt as admin, type this command and hit Enter: netstat –aon
• After that, the output will be displayed and from there, look for the process ID or PID of any program that uses the TCP port 1723 on your computer.
• Next, type this next command and hit Enter: taskkill /PID PID /F
• Once the command has been executed, the concerned program will be forced to close and the TCP port 1723 will be freed up. Keep in mind that the taskkill command ends the process corresponds to the process ID number and the given command above, “/F” option is used to end the program’s process forcefully.
• Now restart your computer and after that, the concerned program should start using a TCP port other than 1723 which leaves the TCP port 1723 free for your internet device to use.

Option 4 – Remove any irrelevant internet device programs

You could also try removing any irrelevant device programs since it is possible that any of these programs could be the one that’s causing the modem to malfunction. These irrelevant programs could be an internet booster or third-party tools that comes with the modem and so on. These programs are not necessarily needed for your modem to function. Thus, if you want to fix the VPN Error 633, you can try uninstalling them and see if it fixed the error.

Option 5 – 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 “devmgmt.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 them.
• 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 the VPN Error 633, 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.

You might have experienced a situation where you’re trying to install or update your Java application on your Windows 10 computer but were not able to do so for some reason. One of the problems you can encounter while updating or installing Java is Error Code 1603. There are two ways you can install Java – you have the option to choose where to get Java either from the online download or offline download. There are times when before you can install Java, you might have to disable the firewall first as it may interrupt the Java online installation. And while doing so, if you are getting the “Java Update or Install did not complete – Error Code 1603” error message, read on as this post will show you what you can do to fix it. At the time of writing, the exact cause of this error is still unknown. On the other hand, you must still check if you have fulfilled all the system requirements needed to install Java. You have to make sure that your Windows 10 PC has sufficient disk space available for the Java installation or update. In addition, you also have to make sure that you meet all the hardware requirements and you are using a popular web browser for the installation, and that you have administrative privileges for download and installation. To fix the “Java Update or Install did not complete – Error Code 1603” error, here are some suggestions you can try.

Option 1 – Restart your computer before you install the new Java package

You might have to restart your computer if you got the error code 1603 while installing Java through an offline download.

• Restart your computer.
• Next, download and install the offline installer of the Java package from the official site of Java and not some third-party source.
• In the prompt box that appears while downloading the Java package, select the option Save in and save the package in your preferred folder.
• After that, navigate to the saved, downloaded package on your computer and then double click on the file to begin the installation process.

After that, if it didn’t fix the problem and you’re still getting the error code 1603, follow the next given option below.

Option 2 – Uninstall the old versions of Java before you install the new package

• Open the Control Panel.
• After that, click on Programs and features.
• Then select the old Java package and click on Uninstall.
• Restart your computer and then try installing the new Java package again from its official site.

Option 3 – Disable the Java content in the browser you’re using via Java Control Panel and reinstall Java

• Open the Control Panel again.
• And then click on the Java icon to open the Java Control Panel.
• Next, navigate to the Security tab and then uncheck the “Enable Java content in the browser” option.
• Then click on Apply and then Ok to save the changes made.
• Now install the new Java package again after you download it from its official website.
• Once the installation is completed, re-enable the “Enable Java content in the browser” option in the Java Control Panel as it is essential especially if you are running Java content in your browser.

Lately, some users reported getting an error that says, “System doesn’t have any USB boot option, Please select other boot option in Boot Manager Menu” when they tried to reinstall the Windows 10 operating system on their PCs or boot from an installation media. If you have the same problem, then this post should help. This kind of error is applicable to multiple devices by various OEMs and is mostly due to the Secure boot being enabled, or the Legacy or CSM support being disabled. It could also be that the bootable USB device was not correctly made and so on. Whatever the cause may be, here are some suggestions you need to check out to resolve the “System doesn’t have any USB boot option, Please select other boot option in Boot Manager Menu” error and reinstall Windows 10 successfully.

Option 1 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve the error. To disable Secure Boot, here’s what you have to do:

• First, boot your computer into Windows 10.
• Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
• After that, go to the BIOS of your computer.
• Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
• Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further options including System restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• Select the UEFI Firmware Settings which will take you to the BIOS.
• From there, go to the Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
• Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
• Save the changes made and exit. Afterward, your computer will reboot.

Option 2 – Try to reset the BIOS or the UEFI Settings

If updating the BIOS didn’t help in fixing Error 0199, you can try to reset the BIOS instead.

• Start your computer and tap the F10 key during the booting process to enter the BIOS. If it does not work, you can try tapping the F1 or F2 key as well as the Del key.
• Once you’re already in the BIOS, tap the F9 key to get the prompt to RestoreLoad default configuration now for the BIOS.
• Next, click on Yes and then follow the next on-screen instructions that appear to set the BIOS back to its default settings.
• Once you’re done restoring the default settings of the BIOS, restart your computer and then check if it now boots properly.

Option 3 – Make a proper bootable USB Drive/Stick

To make a proper bootable USB drive, you need to use the Windows Media Creation tool. The Media Creation tool in Windows allows you to use the ISO installation file to make a bootable device that you can use to install Windows on your PC. Note that this is kind of different from the usual installation process as it could erase your computer’s current settings and data on the primary drive. Thus, before you proceed, you need to backup all your data into some removable drive and then use the Media Creation Tool to make a bootable drive.

• After making the bootable drive, you need to plug it into your computer and then reboot.
• Next, tap the F10 or Esc key to open the boot options.
• Now set the boot priority of the removable drive the highest. Once the setup comes forth, follow the next onscreen instructions and install Windows without any problems.

Option 4 – Try enabling Legacy or CSM boot support

If the Legacy or CSM boot support is disabled, then it’s no wonder why you’re getting an error. Thus, you need to enable it by following these steps:

• Open Settings and go to Update & Security > Advanced Startup options.
• Next, click on Restart Now to reboot your computer.
• After that, select Troubleshoot > Advanced Options where, you will see more options such as System Restore, Startup Repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• From there, enable Legacy Support and then save the changes and exit. This will restart the computer.
• Once your computer has restarted, check if the error is now fixed.

Could not connect to the System Event explanation: Although logging into a Windows 10 computer may seem like a simple process, it’s actually not since the Windows operating system has built a mechanism in a way that any third party or malware intervention would not compromise access to the system. This mechanism is supported by numerous services, functions, and DLL files. And Microsoft has been taking this security to a whole new level with the introduction of Windows Hello. Recently, a number of users reported getting the “Windows could not connect to the System Event Notification Service service. Please consult your system administrator” error when logging into their computers. While some users also reported that although they can log in, they encounter the same error message from the Notification area. There are several options you can check out to resolve the error. You have to check the status of several Windows Services and make sure that they are running. You also have to reset Winsock as well as run the System File Checker scan.

Option 1 – Check for certain Windows Services

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• After that, you will see a list of services and from there, look for the following Windows Services:
  • DHCP Client
  • System Event Notification Service
  • Windows Font Cache Service
• Now make sure that the Startup Type of each service is started and running.

Option 2 – Try resetting the Winsock drivers

• In the Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
• After opening Command Prompt, execute this command: netsh winsock reset

Note: If you are using IPv4, execute the “netsh int ipv4 reset” instead. On the other hand, if you are using IPv6, execute the “netsh int ipv6 reset”

• Now exit Command Prompt and see if the error is now fixed.

Option 3 – Try running System File Checker or SFC scan

You could also run System File Checker or SFC scan to fix the BSOD error. It is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with 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.

• Reboot your PC.

Recently, several users reported an issue on their Windows 10 computers where the taskbar is not visible when they tried to connect to a computer via Remote Desktop Protocol or RDP. The Remote Desktop Connection feature uses the RDP which allows users to access a computer remotely. This is actually different from the taskbar being hidden automatically until the pointer hovers on it since, in this scenario, the taskbar is completely not accessible which makes using the remote computer entirely difficult, if not impossible. There are several suggestions you can check out to resolve this problem, you can try to restart the process of Windows Explorer via Task Manager or you could clear the cache for multiple processes. You could also try to reinstall the Shell Experience components or show the local taskbar in the Remote desktop. Moreover, you could also try to update, uninstall or roll back the display driver/graphics card driver. For more details, refer to each one of the options given below.

Option 1 – Try to restart the Windows Explorer process

The first option you have to try to fix the problem with the taskbar is to simply restart the Windows Explorer process in the Task Manager.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and find the process of Windows Explorer.
• Once you find it, right-click on it and select Restart to restart its process.
• After that, restart your computer and see if you can now see the Taskbar.

Option 2 – Try clearing the cache of multiple processes

The next thing you can do to resolve the problem is to clear the cache of many processes in your computer. To do so, follow these steps:

• Open the Notepad app and paste the following content in the text area:

@echo off taskkill /f /im explorer.exe taskkill /f /im shellexperiencehost.exe timeout /t 3 /NOBREAK > nul del %localappdata%PackagesMicrosoft.Windows.ShellExperienceHost_cw5n1h2txyewyTempState* /q timeout /t 2 /NOBREAK > nul start explorer @echo on

• After that, tap the Ctrl + S keys to save the changes you’ve made in Notepad and select the “All files” as its file type, and then name it “CacheClearTWC.bat”.
• Next, go to the location where you saved the file using File Explorer and then run it. This will run a couple of batch scripts which will clear the cache of multiple processes in the system.
• Tap the Win + X keys and select the “Windows PowerShell (Admin)” option to open PowerShell as admin.
• Next, execute this command in the command line: Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “appxmetadataappxbundlemanifest.xml”)}
• After the command has been executed, this will reinstall the Shell Experience components and should fix the problem with the taskbar.

Option 4 – Update, uninstall or rollback the Graphics card drivers

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in 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. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

One of the errors you can encounter while browsing the web using your Google Chrome browser is the ERR_TUNNEL_CONNECTION_FAILED error. If you happen to encounter this error, then this post could help you resolve it. This kind of error in Chrome can occur due to incorrect website domain configuration, conflicting browser data, incorrect proxy settings, and DNS connection issues. To resolve the ERR_TUNNEL_CONNECTION_FAILED error in Chrome, here are some suggestions you can check out.

Option 1 – Try disabling the proxy server for your LAN

If your PC was just attacked by some adware or malware as of late, it is possible that it has changed the network settings in the system and might display spam advertisements. Thus, you have to disable the proxy server for your LAN. To do that, refer to these steps:

• 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 2 – Try to reset Winsock, TCP/IP & Flush DNS

Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the ERR_TUNNEL_CONNECTION_FAILED error. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 3 – Try using a VPN connection

There are instances when the network that your computer is logged on might have blocked your access to the website you are trying to open and so to fix it, you can try to use a VPN connection. Once you’ve connected using VPN, try to open the website again and see if you can now access it.

Option 4 – Try clearing browser data

There are times when some data in the browser is conflicting with the loading of the website and triggers errors like ERR_TUNNEL_CONNECTION_FAILED. And so you can try to clear your browser’s data. This might be a very basic solution but oftentimes it works in fixing this kind of error in Google Chrome. Follow the steps below to clear the data in your browser.

• Open your Google Chrome browser.
• After that, tap the Ctrl + H keys. Doing so will open a new panel that allows you to delete the browsing history and other data in your browser.
• Now select every checkbox that you see and click on the Clear browsing data button.
• Then restart your Chrome browser and check if you can now open any website or not.

Option 5 – 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.

Note: If removing the browser extensions or toolbars didn’t work, you can also try to reset your Google Chrome browser.

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

Windows 10 has a pre-installed Weather app that offers the local weather information, forecast, temperature gradient, historical data, multiple locations, and many more. It can be handy especially if you tend to check on the weather. However, if you are one of those users who barely use this app, you have the option to uninstall it from your computer and that’s exactly what we’re going to do in this post. There are several methods to uninstall the Weather app in Windows 10. You can uninstall it via Settings or Start Menu or even using a command in Windows PowerShell. Note that uninstalling the Weather app does not affect the functionality of your Windows 10 computer by any means so you shouldn’t worry about uninstalling it. To get started, follow the instructions provided below.

Option 1 – Uninstall the Weather app through Settings

The first option you can try to uninstall the Weather app is through Settings. It’s a very simple process so you wouldn’t have any trouble following it.

• First, click on the Start menu and go to Settings.
• From there, select System > Apps & Features.
• After that, wait until the list of apps is opened, and then look for the Weather app and click on it.
• Next, click on Uninstall in the given menu to uninstall the Weather app from your computer.

Option 2 – Uninstall the Weather app through the Start Menu

Another simple way to uninstall the Weather app is through the Start Menu. It only takes a right click and there are actually two ways to go about this – one is new with the recent feature update of Windows. How? Refer to these steps:

• Click on the Start button and type in “weather” and right-click on the Weather app which appears in the list.
• Next, click on the Uninstall option. This will uninstall the Weather app.
• You can also use the other uninstall option which you can find on the right side of the list that also shows other quick action for the app.

Option 3 – Uninstall the Weather app through a command in Windows PowerShell

• Tap the Win + X key combination and click on the “Windows PowerShell (Admin)” option to open PowerShell with admin privileges.
• After that, execute the following Remove App package command for the Weather app to uninstall it.

Get-AppxPackage Microsoft.BingWeather | Remove-AppxPackage

• Once done, it will remove the Weather app from your computer.

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.