A Quick Guide to Fixing Error Code 10

Error Code 0xc0000001 – What Is It?

Error code 0xc0000001 on Windows 10 has been reported by some users when attempting to install Windows 10. When you encounter this error, the setup will be in a loop and the error message will keep popping up.

Solution

Error Causes

If you encounter the error code 0xc0000001 while trying to install Windows 10, it most probably be due to corrupted installation file. However, it can also be caused by any of the following:”

• Damaged SAM file
• Damaged system files
• File system integrity compromised
• Damaged RAM

Further Information and Manual Repair

Here are some methods that will help you fix the error code 0xc0000001 while trying to install Windows 10. Do not perform these methods unless you’re absolutely confident you can do it properly. Otherwise, you might make things worse.

If you’re not that confident, consider seeking advice from a technical expert. If you can’t afford one, you may want to consider getting an automated software to fix the job.

Method 1: Convert drive/partition to GPT

If you need to manually wipe the drive and then convert it to GPT, follow these steps:

• Step 1: Power down your computer and put your Windows 10 installation DVD or USB drive
• Step 2: Boot your computer to the USB or DVD key in UEFI mode.
• Step 3: Once you’re at the Windows 10 Setup, press the Shift+F10 keys. This will open the command prompt window.
• Step 4: Open diskpart tool from CMD. Just type diskpart and enter.
• Step 5: Then, type the list disk on CMD again. Press enter. This will allow you to identify your computer’s drive that you want to reformat.
• Step 6: Choose the drive and reformat it by typing the following on the command prompt:

select disk <disk number> (press enter)

clean (press enter)

convert gpt (press enter)

exit (press enter)

• Step 7: Proceed with the Windows 10 Setup installation.

Note: when you’re prompted to choose the installation type, make sure to choose Custom. Then, choose unallocated space and click Next. This will automatically start the installation of Windows 10.

Method 2: Use Media Creation Tool to Perform Automatic Repair

Automatic Repair is a Windows feature/utility that allows you to fix certain system problems preventing you from installing or starting Windows. It works by scanning your computer system for any potential problem and tries to fix it.

• Step 1: Download the Media Creation Tool
• Step 2: Boot your computer using the Windows 10 DVD, or the System Repair disc. When you’re asked to press any key to boot, just press any key on your keyboard.
• Step 3: Choose the right time and the keyboard type.
• Step 4: Click Repair your computer. You’ll see this in the lower-left corner of your screen.
• Step 5: Choose Troubleshoot from Choose an option screen
• Step 6: Click Advanced options
• Step 7: Choose an automatic repair

This will automatically run the utility.

Method 3: Check Hardware Devices

Another possible reason why you are getting this error while installing Windows 10 is due to the connected external hard drives. To fix this, power down your computer. Afterward, unplug and remove all connected external hard drives. If you’re using USB device to install Windows 10, ensure your BIOS is set to boot your computer from the USB.

Method 4: Create New Copy of Windows 10 Installer

Another possible reason why you experience this error is that your copy of the Windows 10 installer is corrupted. To fix this, it’s better to create a new copy of the Windows 10 installer.

• Step 1: Go to this link
• Step 2: Click the Download tool now. Choose Run with admin privileges
• Step 3: On What do you want to do? section, choose installation media for another PC. Click Next.
• Step 4: Select edition, language, and architecture (32-bit or 64-bit).
• Step 5: Choose the media you want to use. If you want to use a USB flash drive, make sure the device at least has 5GB of free space. If you’re using an ISO file, you need to save the file first on your computer and then burn the file to a DVD.

Method 5: Use a Powerful Automated Tool

If you still encounter these errors after performing the above methods, find a trustworthy automated tool. As long as the automated tool is powerful and reliable, it will help you fix this error.

As you know, Microsoft constantly releases new updates with the main goal of fixing bugs as well as deliver users with new and exciting features. However, there are times when the latest update comes with an unwanted bug. One of these bugs is an error message saying, “Low Disk Space. You are running out of disk space on Local Disk (G:). Click here to see if you can free space on this drive.” So if you have recently installed a Windows 10 update, then you’ll most likely see a completely new drive on your computer which will appear right after the installation of the update and you’ll also start seeing the aforementioned error message. It gets irritating as this error message keeps on popping up even if you still have a lot of free space on your other drivers. Obviously, the main reason why this error message pops up all the time is the bug brought along by the Windows Update. This bug unhides the recovery partition drive and allocates it a drive letter which is why you are seeing a new drive in your computer. Thus, you can get rid of the pesky error message by simply removing the letter of the new drive. Just remember that you must not delete anything from the recovery partition drive nor format the drive. Formatting or deleting the recovery partition drive can heavily affect the recovery of Windows since the data on the drive is used by the Windows Recovery Environment or your system’s manufacturer. A lot of users have reported that removing the drive letter has resolved the issue. And if you worry that removing the drive letter will delete the drive, you are mistaken. This solution is basically harmless and is proven effective to make the notifications go away. Carefully follow the instructions below to get rid of the Low Disk Space notification by removing the drive letter.

• Step 1: Tap the Windows key once.
• Step 2: Next. In the Windows Start Search, type in “command prompt” and right-click on Command Prompt from the search results and select the “Run as administrator” option or you could simply tap Win + R keys and then input “cmd” and hit Enter to open Command Prompt.
• Step 3: After opening Command Prompt, type in “diskpart” and tap Enter.
• Step 4: Next, type in “list volume” and tap Enter. After that, you will see a list of drives.
• Step 5: Take note of the letter associated with the newly created drive.
• Step 6: Afterwards, type in “select volume <drive letter>” and tap Enter. Take note that you must replace the <drive letter> with the drive letter you’ve found in Step 5.
• Step 7: Now type in “remove letter=<drive letter>” and then tap Enter. Once again, replace the <drive letter> with the letter you took note of in Step 5.

What Is 0x00000050 Stop Error?

While running your Windows 7/Windows Server 2008 R2, your system suddenly stops responding out of complete randomness and you see an error message popping up which says something like this:

0x00000050 (parameter1, parameter2, parameter3, parameter4)

Solution

Error Causes

The stop error 0x00000050 signifies that there’s a PAGE_FAULT_IN_NONPAGED_AREA problem. If you’ve seen this error on different occasions then you will find the parameters in the message to be varying. That is because they are dependent on your PC’s configuration. Not all Stop errors "0x00000050” occur due to a single issue.

However, the most common problem which is encountered which results in the stop error popping up is due to a pool corruption occurring in the Srvnet.sys file.

This issue might be caused because of software incompatibility or a defective physical memory which resulted in requests for data for a hardware driver or service which was not found in the memory.

If you find the error occurring after you’ve installed a new application or a device driver then you should access Safe Mode and uninstall, disable or remove that application or driver.

Further Information and Manual Repair

In order to fix this issue, you should try booting your computer to the “Last Known-Good Configuration” as listed during startup.

For this you have to follow the below-mentioned steps:

1. Start your system.
2. When you see the message which says “For Troubleshooting And Advanced Startup Options For Windows, Press F8” hit F8 and proceed.
3. Use the up and down arrow keys to highlight “Last Known-Good Configuration” and hit enter (This method will only work if your system boot was not successfully carried out ever since you made any specific changes).
4. When you are starting the computer, press F12 and proceed with the PSA/32 Bit Diagnostics.
5. Do the following so that a clean boot can be performed:

• Go to the Start menu when the Windows 7 desktop shows up.
• On the search bar, type “msconfig” and hit search.
• Disable all the applications which are listed on the “Startup” tab.
• Now head over to the “Services” tab and mark the option which reads "Hide all Microsoft Service".
• Select the “Disable All Services” option.
• Apply the changes by clicking on “Apply” then restart your PC. You should now check the performance of your computer. If you don’t see a BSOD then you start re-enabling all the Services and Startup applications one by one until you finally figure out which one is causing the BSOD to appear.

6. Update your Windows with “Windows Updates”.

The Windows Subsystem for Linus, also known as WSL, is a useful and excellent tool for developers. However, it isn’t without flaws as users can still encounter some errors when using it. One of these errors is the error code WslRegisterDistribution, 0x8007019e,0x8000000d. Although it seems like the error is have something to do with the installation of WSL, it could be a false positive since some users who’ve installed WSL still encountered the same problem. Here’s the context of the error:

“Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007019e/0x8000000d Error: 0x8007019e/0x8000000d The parameter is incorrect. Press any key to continue.”

Error code 0x8007019e or 0x8000000d could be due to the absence of supporting Windows 10 features since the error does not even let one use the WSL-based command line. If you are one of the users facing this problem, then you’ve come to the right place as this post will provide you with a couple of suggestions to fix it. There are two options you can check out to fix the problem, but before you do that, you need to make sure that the Windows Subsystem for Linux feature is enabled. The two options include enabling WSL using the “Turn Windows features on or off” option and using the Windows PowerShell.

Option 1 – Try to enable the WSL using the “Turn Windows features on or off” option

• To get started, search for “Turn Windows Features on or off” in the Start Search and click on the appropriate result to open a dialog box.
• After that, you will see a populated list in the dialog box and from there, look for the “Windows Subsystem for Linux” option.
• Once you find it, select OK. This will search and install the system files needed and ask you to restart your computer.
• Restart your computer. The Linux distro should now work without any trouble.

Option 2 – Try to use Windows PowerShell

The next thing you can do to fix the error code 0x8007019e or 0x8000000d is to use Windows PowerShell.

• Tap the Win + X keys and click on the “Windows PowerShell (Admin)” option to open Windows PowerShell as admin.
• After that, execute this command to enable the Windows Subsystem for Linux feature: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
• The command you entered will start to search for the required system files and install them.
• If prompted, type “Y” to restart your computer. This should fix the problem.

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.

Error Code 0x8007007b – What is it?

This error code occurs when users fail to activate their Windows operating system. It is one of the more popular Windows error codes since it affects many versions of Windows including Windows 7, Windows 8.1, and Windows 10. Error code 0x8007007b has common symptoms which include the following:

• Inability to activate a Windows installation
• Message box highlighting error code 0x8007007b

Solution

Error Causes

Error code 0x8007007b in Windows 8.1 usually results due to one or more main clauses. Windows 8.1 users may experience this error due to the use of volume-licensed media. The error code may also arise if the activation wizard is unable to connect to Key Management Service (KMS) host computer or if corrupted system files are present on your computer.

Further Information and Manual Repair

Windows error codes such as Error code 0x8007007b can be a complicated issue, requiring the use of technical knowledge and skills. For this reason, we have listed instructions in the simplest of forms to enable even average users to successfully complete manual repair methods that will resolve error code 0x8007007b.

The same approach has been applied to all our error code solutions. See also Error Code 0x00000024 and Error Code 0x80004005.

Below are the two main methods for correcting this issue.

Method One: Use Multiple Activation Key (MAK) to Activate Windows

This method involves the use of a Multiple Activation Key (MAK) instead of the Key Management Service (KMS) to activate the Windows operating system you intend to use on your PC. This manual repair method requires the use of Command Prompt so ensure you follow the instructions provided carefully so as to avoid the risks of causing harm to your system.

• Step one: Select Windows log key + X.
• Step two: Click Command Prompt, then Admin
• Step three: Type in admin password if Command Prompt requests it
• Step four: Type slmgr -ipk followed by the MAK product key. Note that the product key should have 25 characters with dashes between them like this xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Attempt to activate your Windows installation once you’ve completed the exact instructions above. If you are unable to complete this process, consider getting help from a Windows repair technician or simply move to the next manual repair method listed below.

Method Two: Run System File Checker

System File Checker (SFC) enables Windows users to scan and repair errors or corruption on system files. Since such errors within your system files can cause error code 0x8007007b to occur, follow the steps below to fix this error code.

• Step One: Go to Start and type Command Prompt or CMD.
• Step Two: Run as Administrator
• Step Three: Type sfc /scannow with a space between “sfc” and “/scannow”.

The System File Checker tool will begin scanning your machine for corrupted or missing files in need of repair. If these files are found on your system, the tool will repair and replace them. Once this is done, restart your computer then check to see if you can now activate your Windows operating system.

Method Three: Use an Automated Tool

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

Counter strike has evolved from half-life mod into the full-featured game and has kept in popularity for years, even today game is wildly popular and has a huge player base. Sadly game can crash in Windows 10. Here in this article, we will address how to fix csgo crashing in Windows 10 so you can play it smoothly and crash-free as it was meant to be played.

1. Update your display drivers

   Often in the gaming world having the latest display drivers can mean a world of difference. Counterstrike GO is no different, make sure that your drivers are updated to the latest version, if they are not, go to your manufacturer's website and download the latest version.

2. Update Windows

   Just how much important is it to have the latest display drivers so it is to have the latest Windows update. Often problematic things are addressed in the update itself.

3. Turn off compatibility mode

   Compatibility mode is most often the cause of crashes. Go to the game installation folder and search for csgo.exe. Once you locate it right-click on it and choose properties. Under properties, find the compatibility tab and turn off compatibility mode if it is ON. Uncheck run as administrator also

4. Delete CSGO.EXE and add cl_disablehtmlmotd 1

   If disabling compatibility mode has not solved the issue do next: Pull up the installation directory folder, find csgo.exe, and delete it Pull up the Steam Library and locate Counter-Strike Global Offensive Right-click on it to select properties Find the local tab and click on verify integrity of game files When that is complete, go back into the Counter-Strike Global Offensive installation folder and search for cgo.exe Turn compatibility OFF like in the previous step Return to the Steam Library, right-click on Counter-Strike Global Offensive and click on properties again Go under the launch options settings In the new window, type in cl_disablehtmlmotd 1 Save the changes and restart the game

5. Lower game settings

   If previous steps did not help and the game still crashes, try lowering game graphic settings. Crashes can happen if a game is heavy on the current system resources.

What is SYNTP.SYS file? it is a system file created by Synaptics Touchpad drivers that are responsible for all the gestures and tracking users’ touch on the Touchpad. However, what happens when this driver fails? Well, it’s either that your touchpad will partially stop working or it will completely stop working at all. And in such cases, you will encounter the SYNTP.SYS Blue Screen error along with any of the following error codes:

• IRQL_NOT_LESS_EQUAL
• KMODE_EXCEPTION_NOT_HANDLED
• INVALID_PROCESS_ATTACH_ATTEMPT

To resolve the problem, use the instructions given below as a reference.

Option 1 – Run the Memory Diagnostic Tool to check for Memory leaks

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 2 – Try reinstalling the Synaptics Driver

You might want to reinstall the Synaptics driver to resolve the SYNTP.SYS Blue Screen error.

• Tap the Win + R keys to open the Run dialog box.
• After that, type “appwiz.cpl” in the field and hit Enter to open the Programs and Features section in the Control Panel.
• Next, you have to look for the “Synatics Point Device driver” and right-click on it, and then click on Uninstall to remove it from your computer.
• Restart your PC and then check for updates under the Windows Update section.
• After that, it will find the latest available and stable Synaptics driver and then install it.
• Then click the “Check or Updates” under the Windows update section and it will automatically look for the latest available Synaptic driver and install it for you.
• Now restart your PC and for the changes to take effect.

Option 3 – Try to run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the Error 0x80000003. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Restart your computer after the scan is completed.

Option 4 – Perform a System Restore

Performing System Restore might help you in fixing the SYNTP.SYS Blue Screen error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 5 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the SYNTP.SYS errors. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

• Wait for the process to be completed and then restart your computer.

Option 6 – Use the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like SYNTP.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.

Each you connect time external devices like scanners, printers, and the likes to a Windows 10 computer, the device either pushes the drivers through the USB or any other port, or you are expected to install the drivers through external media. In both cases, the driver will be loaded into the system, allowing you to use the device. However, it doesn’t always go smoothly as you could encounter some errors like the “Windows cannot load the Device Driver for this hardware because a previous instance of the Device Driver is still in memory ( Code 38 )”. If you encounter such an error in the Device Manager, then this means that a previous version of the device driver is still in memory and that each time the device is used, that previous version is loaded into memory and then unloaded which triggers the “Windows cannot load the Device Driver for this hardware because a previous instance of the Device Driver is still in memory (Code 38)” error. This kind of error occurs if the operating system loads the unwanted driver or if it fails to unload the driver. It could be that there is an obsolete version of the driver that’s still installed in the system or it could also be that you need to update your USB drivers as they could be outdated or the problem could also be due to some third party program that is interfering with the installation. Whatever the cause is, here are some suggestions you can check out to resolve the problem.

Option 1 – Uninstall previously installed drivers and reinstall their latest working version from the manufacturer’s website

The first thing you can do is to uninstall the drivers that are currently installed on your computer and then reinstall their latest working versions from their official sites. This kind of error is commonly encountered while loading drivers for scanners and printers. This is due to the fact that their drivers and software come along with a package which is usually in external media like CD or DVD. So when you install the software package, there’s a possibility that a newer version has been launched by its manufacturer. When that happens, you have to uninstall the previously installed driver package and then download the drivers from the manufacturer’s website and install them.

Option 2 – Run the Hardware and Devices Troubleshooter

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Option 3 – Update or reinstall the Universal Serial Bus Controller driver

Since it could be a driver issue, you can try to update or reinstall the Universal Serial Bus Controller drivers using the Device Manager. Refer to the following steps:

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.

Note: If it is a regular USB drive, then it will be listed as a USB Mass Storage Device but if you have a USB 3.0 device, then look for a USB 3.0 Extensible Host Controller.

• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 4 – Restart your computer in a Clean Boot State

If the first three given options didn’t work and you still see the error when you connect external devices, you can try putting your computer in a Clean Boot State and then try connecting them again.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• Now try to connect the external devices and check if the error is now gone.

What is Error 0x00000024?

Error 0x00000024 can be seen when you start up and a screen comes up asking which mode you would startup in. Regardless of the mode you select, it leads up to the Windows screen with the loading bar and your computer crashes from there onwards. When you press F8 in order to select the “Disable Automatic Restart On System Failure” option, that is when this error shows up:

ST0P 0X00000024 (x00190203, 0x82700550, 0xc000012, 0x00000000)

Due to this error, both Safe and Normal modes become inaccessible.

Solution

Error Causes

If you’re having this error then it is the indication of an issue with the file NTFS.sys. Further, there might also be problems with the IRP (Interrupt Request Packet) or the disk may have been corrupted. There are multiple other causes of this error, including heavy fragmentation of your hard drive or problems caused by your antivirus software.

Further Information and Manual Repair

First and foremost, you are suggested to run Chkdsk. In order to do this, you have to enter your BIOS and select CDROM as your primary booting device. Now follow the below-mentioned steps:

1. Insert your Windows XP installation CD into the CDROM and reboot your PC.
2. Press any key to proceed with the boot from CD when you are prompted to do so.
3. When the Windows XP setup menu shows up, hit the “R” key to proceed with repairing Windows.
4. If there is only one Windows installed on your computer then hit the “1” key and proceed by pressing enter. If there are more than two Windows then hit the number which is associated (according to the screen you are viewing) to the Windows you want to repair. Usually, this is C:/Windows and associated with “1” but if that is not the case then you should simply press the number that corresponds with the windows you want to repair and proceed.
5. Now, you will see a screen that prompts you to enter your administrator password. Most people don’t have an admin password and in that case, you should simply hit enter and you’d be good to go. If you do have an administrator password, however, then you should type it in, hit enter, and proceed.
6. When the DOS prompt shows up, type in chkdsk/f and hit return.

If you see no improvement in solving Error 0x00000024, and the problem keeps persisting, then you should start over. But this time you should type sfc/scannow instead of chkdsk/f and hit return. There are a few other complex methods that you can try as well but this is the most recommended procedure as it is easier, quicker, and most likely to fix the error.