Fix Can’t Find Games on Twitch

Every time a new drive or any storage device is connected to a Windows 10 computer, the operating system tends to allot a drive letter to it automatically. Not only that, as the OS also maps the location of the drive which helps it point the letter to the exact port location of the drive and serve requests from the user. As a result, it builds up a bit of cache as per the pattern in which the user uses the storage of the computer. This whole process is known as “Auto Mounting” which works for hard disks or optical drive readers that are connected using the SATA ports and even for USB drives that are connected using the USB ports. There are several ways you can enable or disable the Auto-Mount feature in Windows 10. You can do it using the MountVol tool or the Registry Editor or the Diskpart utility. Before you proceed, it is recommended that you create a System Restore point first so that you can always undo the changes you made in case anything goes wrong.

Option 1 – Enable or disable Auto Mounting via MountVol tool

In this option, you will be using the mountvol command in the Command Prompt. Refer to the steps below.

• Tap the Wins key once and type in “command prompt” in the field.
• From the search results, right-click on Command Prompt and select the “Run as administrator” option to run it with admin privileges.
• Next, type the following command and tap Enter to enable the Auto Mount feature:

mountvol /E

• On the other hand, if you want to disable the Auto Mount feature, type the following command instead:

mountvol /N

• After that, type the command below to remove all the previously assigned drive letters:

mountvol /R

• Finally, restart your computer.

Option 2 – Enable or disable Auto Mounting via Registry Editor

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and tap Enter to open the Registry Editor.
• After that, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesmountmgr
• Next, look for a DWORD named “NoAutoMount”. If you can’t find a DWORD with that name then simply create a new DWORD with the same name and make sure that the base is selected to Hexadecimal.
• Now double click on that DWORD and change its value to 0 if you want to enable it, otherwise, input 1 as its value to disable it.
• Restart your computer.

Option 3 – Enable or disable Auto Mounting via Diskpart utility

• Tap the Wins key once and type in “command prompt” in the field.
• From the search results, right-click on Command Prompt and select the “Run as administrator” option to run it with admin privileges.
• After opening Command Prompt as admin, type the following command and hit Enter to launch the Diskpart utility:

diskpart

• After that, a User Account Control prompt will appear. Just click on the Yes button.
• Next, type the following command and hit Enter:

automount

• Following the command you entered, you will an output that either says, “Automatic mounting of new volumes enabled” or “Automatic mounting of new volumes disabled” which means you can use it to check the status of Auto Mount.
• Now if you want to enable the Auto Mount feature, type the following command and tap Enter:

automount enable

• And if you want to disable the Auto Mount feature, just enter the following command:

automount disable

• To remove all the assigned letter and history of drives that were connected previously, type the following command:

automount scrub

• Finally, restart your computer.

Error Code C19000101 - 2000B on Windows 10– What is it?

Error Code C19000101 - 2000B is a Blue Screen of Death (BSOD) error encountered by Windows users in an attempt to upgrade their operating system from Windows 7 or Windows 8/8.1 to Windows 10. The system upgrade does not successfully finish and when the installation is resurrected, it fails then reverts back to the original operating system. More and more Windows users come across this error that may have been triggered by a few reasons to be discussed in this article.

Solution

Error Causes

Microsoft users can experience the BSOD error C19000101-2000B due to the following reasons:

• There’s an incompatibility with the drivers
• Antivirus software

Further Information and Manual Repair

In fixing error code C19000101-2000B, you can try doing it manually. Manual repair methods can offer users solutions effectively and efficiently, having to address the root causes and issues in relation to a number of Windows error codes. If properly implemented, these manual repair methods can help Windows users resolve problems at hand immediately. However, there are cases where the help of a Windows professional is necessary. In such instances, it would be best to consult a certified Windows expert or you can also try using a powerful automated tool whenever needed.

To be able to fix error code C19000101-2000B, implement the first method used in resolving error code 0xc000021a, then you can proceed with this first method:

Method One: Perform Clean-Boot

1. Prior to performing an upgrade, you need to disable your antivirus. Or, better yet, uninstall it.
2. Ensure that your PC name is simple without hyphens, periods, or dashes.
3. Restart your device several times, then try again.
4. Disable all USB devices such as a smart card reader.
5. If you are using a SCSI hard disk, be sure to have the drivers ready and available for a storage device like a thumb drive to be connected. While on the Windows 10 setup, select the Custom Advanced Option then use the Load Driver command to load the right driver for the SCSI drive. If the setup still fails, try switching to an IDE-based hard disk.
6. Launch a clean boot, restart your device, then try again.
7. If you are upgrading to Windows 10 using the .ISO file, make sure to disconnect from your internet connection during setup. If your device is connected by Wi-Fi or through LAN, you need to disable both before attempting to run a  system upgrade again.
8. Switch to a local account if you are connected to a domain.
9. Ensure that all external devices such as USB keys, external hard drives, gaming controllers, or printers are not attached to your device.

If you are upgrading to Windows 10 using Windows Update, you can perform a manual repair using the next method.

Method Two: Upgrading Via Windows Update

1. Make sure to disconnect from the Wi-Fi or LAN once the download reaches 100% before you proceed with the system upgrade.
2. Press Windows + X to open the command prompt window as an administrator.
3. Stop the Windows Update service, BITS, MSI Installer, and Cryptographic by inputting the following commands one by one, hitting Enter after every command:

Net stop wuauserv

Net stop bits Net stop msiserver Net stop cryptSvc

4. Restart both Software Distribution and Catroot2 folders. You can do this by typing Ren C: WindowsSoftwareDistribution SoftwareDistribution.old and Ren C: WindowsSystem32catroot2 Catroot2.old in the command prompt to change the names of both Software Distribution and Catroot2 files.
5. Restart the Windows Update service, BITS, MSI Installer, and Cryptographic by inputting the following commands one by one, hitting Enter after every command:

Net start wuauserv

Net start bits Net start msiserver Net start cryptSvc

6. Exit the command prompt then restart your device. You can now try to proceed with the system upgrade again.

Method Three: Disable or Uninstall Antivirus

1. If you opt to just disable your antivirus, you just have to right-click on the antivirus’ icon from your toolbar then choose Disable.
2. Press Ctrl + Alt + Del to open the Task Manager.
3. Check if all the files or services linking to your antivirus are turned off.
4. If you choose to uninstall your antivirus (which is recommended), open Control Panel.
5. Once the Control Panel window is open, select Programs then Uninstall a Program.
6. Look for your antivirus on the list, right-click it then choose Uninstall.

There has been recently discovered in the field of malware targeting Android devices. Affecting more than 10 million users of Android phones, the malware GriftHorse is doing its attacks via phishing and premium services scams. A lot of applications have been discovered that are hosts for this malware and many of them are inside the Google store and available for download. According to Zimperium zLabs, this malware that was recently detected has been doing its scams and attacks even in November of 2020 and has thus far accumulated hundreds of thousands of dollars in its scam. On the surface it looks very harmless, asking for typical permissions like internet access, calls, and other related needed functions, and then it waits. After few months the real attack happens when users get charged with premium service they never subscribed to in the first place.

List of Infected Applications that Carry GriftHorse Trojan

Zimperium zLabs listed out some of the apps with this malware. Users are advised to avoid installing them.

•     Amazing Video Editor
•     Bag X-Ray 100% Scanner
•     Bus – Metrolis 2021
•     Call Recoder Pro
•     Call Blocker-Spam Call Blocker
•     Cinema Hall: Free HD Movies
•     Coupons & Gifts: InstaShop
•     GPS Phone Tracker – Family Locator
•     Fingerprint Changer
•     Fitness Point
•     Free Calls WorldWide
•     Geospot: GPS Location Tracker
•     GPS Phone Tracker – Family Locator
•     Handy Translator Pro
•     Horoscope : Fortune
•     iCare – Find Location
•     iConnected Tracker
•     Instant Speech Translation
•     Lifeel – scan and test
•     My Chat Translator
•     My Locator Plus
•     Plant Camera Identifier
•     Racers Car Driver
•     Safe Lock
•     Screen Mirroring TV Cast
•     Slime Simulator
•     Smart Spot Locator

These are only some of the many infected apps available on the internet. Zimperium zLabs also warned that GriftHorse Trojan exists in over 70 countries worldwide. The infected app quickly changes the language and displays content depending on the user’s IP address.

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

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

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.

OneXPlayer is a direct competitor to Valve’s upcoming steam deck. This device is clearly inspired by Valve’s offering and it shows all over the place, from its looks to its purpose and aims to PC gamers as a handheld device.

Hardware under the hood

This device is packing a 7-inch 1080p display, 11th generation Intel Core i7-1195G7 CPU, stunning 16GB of RAM, 512GB SSD drive with the option to purchase 1TB or 2TB model. GPU of choice is Intel iris Xe Graphics that is in our opinion a bottleneck in the whole system and for more demanding games, we believe switching them to 720p would be a better option. Everything here is powered with a 10455 mAh lithium-ion battery.

OneXPlayer inputs and other stuff

Handheld is equipped with dual bumpers and dual linear triggers. The console comes with dual speakers on both sides of it. Inside the console, there is an aluminum heat sink with copper heat pipes and a fan in order to cool internal hardware. On the outside, we have two USB-C ports and one USB-A port for connections, and of course, a headphone jack for headphones. The console comes with Wi-Fi 6 and Bluetooth 5.0 for wireless connectivity.

Price

The base entry model will cost you a whopping $1.259, 1TB model $1.399 and 2TB one will go as far as $1,599. With this kind of price, I am not sure it can come up as a winner against Valve. Sure it is packing fully licensed Windows 11 that will for sure offer more options than Stem’s OS based on Linux but even with that advantage I do not think it justifies such a big price difference.

Conclusion

Of course, this kind of console or handheld PC will still find its customer base, many users will probably like it since it comes Windows ready out of the box. Sure, you can place Windows on Steam deck as well but you will need to know how, where everything is ready and you can run beside steam other launchers without issues like origin, uplay, gog, etc. How this will be accepted by community time will tell but it is good to see that there is variety and competition in handheld PC space.

You might have experienced a situation where your Windows computer was interrupted due to some battery issues or power failure. It could be that the upgrade process was interrupted because you’ve signed out of your computer or you restarted it by accident. In this case, you will most likely get a Windows Update or Upgrade error 0x80200056. If you are getting this error, read on as this post will guide you in fixing it. This kind of error pops up when the upgrade process was interrupted and could be caused by anything but the baseline here is that your computer was restarted accidentally or someone could have signed out your PC. To resolve the problem, here are some fixes you ought to try:

Option 1 – Try updating or upgrading your computer again

This is the basic thing to do since the process was suddenly interrupted. Just log in to your account and restart the Windows Update or Upgrade process but make sure that your internet connection is stable and that you don’t touch anything so as not to interrupt the upgrade/update process again.

Option 2 – Check if your PC is plugged in or if the battery is full

It is always best to update your computer always when you’re really sure that the power won’t fail. If you’re using a desktop computer, make sure that everything is plugged in. And if you’re using a laptop when this error occurred, make sure that its battery is at 100% but it’s better if you just plug it into power just in case as there are times when the Windows update or upgrade gets stuck for too long like for hours so it will really help if your device is connected to power.

Option 3 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update errors as well as the error 0x80200056. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button.

Option 4 – Delete the contents in the SoftwareDistribution folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. A lot of users tried deleting the files in this folder to fix the problem and so far it has worked. Like them, you can try clearing the Windows Update cache by simply deleting the contents of the folder named “SoftwareDistribution” since Windows apparently can’t clear and re-download the update contents once they are corrupted. Thus, deleting the contents of this folder will make Windows download the contents again which will fix the problem. To do that, follow the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• Next, got to the C:\Windows\Software\Distribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

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

Option 5 – Try running the System File Checker scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be causing the error 0x80200056. 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.

Option 6 – Run the Chkdsk utility to repair hard disk errors

You can also run the Chkdsk utility to resolve the Windows Update error 0x80200056. 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 commands listed below, and don’t forget to hit Enter right after you type in each one of them and if you have installed Windows to some different directory, you must replace “C” with the name of the drive you’ve installed Windows with.
• chkdsk C: /r /x
• chkdsk C: /f

Option 7 – Run the DISM tool to repair the Windows Update client

The Windows update/upgrade error 0x80200056 might be caused by some issues in the Windows Update client so you need to run the DISM tool to repair it. Note that you have to use another computer or another Windows from a shared network to fix it.

AVFoundationCF.dll is a type of Dynamic Link Library file. This DLL file is associated with AVFoundationCF and is developed by Apple Computer Inc. for Windows PC. This file functions similarly to any other DLL files. It comprises of small programs. This DLL file is typically needed to load and start the Apple iTunes utility. The inability to call this file or the files to load triggers the AVFoundationCF.dll error message on your system. The error message can be displayed in either of the formats on your PC:

“The program can’t start because AVFoundationCF.dll is missing from your computer. Try reinstalling the program to fix this problem.” "This application failed to start because avfoundationcf.dll was not found.” "Cannot find %COMMONFILES%AppleApple Application Supportavfoundationcf.dll." "Cannot start AVFoundationCF. A required component is missing: avfoundationcf.dll.” “Avfoundationcf.dll Access Violation." "Cannot register avfoundationcf.dll."

Solution

Error Causes

AVFoundationCF.dll error can occur due to numerous reasons. However, the most common reasons for this error code include:

• Viral infection
• Corrupt or invalid registry entries
• Apple Computer Inc. hardware failure such as bad hard drive
• Missing or deleted Avfoundationcf.dll file

It is recommended to resolve the error as soon as you experience it virtually because if the error code is related to viral infection on your system, it can expose your PC to privacy errors and data security risk. And if the error is triggered by registry issues, it can lead to serious threats like system crash, failure, and data loss. Therefore, the AVFoundationCF.dll error not only hampers your ability to access and start Apple iTunes program but it also puts your PC at serious risk.

Further Information and Manual Repair

To fix the error AVFoundationCF.dll on your PC, here are some of the best and easy to do solutions that you can try:

Check your Recycle Bin

Since dll files are shared files, there is a possibility that this file accidentally got deleted when you were uninstalling some other program on your system. If you experience missing AVFoundationCF dll file error message after performing any program on your PC, then chances are that it got deleted and maybe in your recycle bin. So, first, check your recycle bin and search for the dll file. If you find it, restore it to fix the error.

Update Device Driver

To resolve the issue, try performing a driver update. This can be done by downloading the latest drivers from the hardware manufacturer’s website. Now open Device Manager from the Control Panel and locate the hardware device that you want to update the driver for. Once you find the hardware you are updating the driver for, right-click on the hardware icon and choose properties. In the properties windows, click the driver tab. Now click the update driver button. To activate changes, restart your PC. To automatically update your computer's drivers when necessary, download and install DriverFIX.

Try Re-installing Apple iTunes Program

To do this, simply go to the control panel, select programs and then uninstall a program and then select iTunes.  Uninstall it and then repeat the same program and install the Apple iTunes program again on your PC by downloading the program from Apple’s official website.

Scan for Viruses

If the error still persists, then it is advisable to scan your PC for viruses. This can be easily done by running a powerful antivirus on your PC. However, please note anti-viruses are notorious for slowing down PC performance. So, may have to compromise on the speed of your system.

Clean and Repair the Registry

If the error is caused by invalid and corrupt registry entries and damaged Avfoundationcf dll file, then the best way to resolve is to download a powerful registry cleaner. We advise you to install Restoro on your PC. This is an advanced and a multi-functional PC Fixer integrated with multiple powerful utilities including a high functional registry cleaner, an antivirus and a system optimizer. The registry cleaning utility scans all the registry issues and removes all errors triggered by the registry immediately. It cleans the registry by wiping out all the unnecessary, obsolete and redundant files including invalid entries and bad registry keys. Furthermore, it also fixes the damaged and corrupt dll files including Avfoundationcf dll file. Thereby resolving the error right away. Furthermore, the antivirus deployed in this software scans for all types of malicious codes like viruses, Trojans, spyware, and malware and removes them. To ensure you don’t compromise on your PC performance, it is deployed with a system optimizer utility that boosts the speed of your computer dramatically. This tool is bug free, has a user-friendly interface and compatible with all Windows versions. Click here to download Restoro and resolve Avfoundationcf.dll error on your PC today!

There are instances when you might encounter an error that says, “Something went wrong, We couldn’t start your program” when you open any Office program. This could be due to an issue with the Office file and any Office app you open throws the same error message. This applies to Office 2019/2016, Office 365 Home, Office for Business as well as Business editions. In this post, you will be guided in what you can do to resolve this error. There are several potential fixes for this error, you might only have to restart your computer or you may have to repair Office from Apps and Features or you could also uninstall and install it back again. For more details, follow each one of the provided options below.

Option 1 – Restart your computer

You might be unable to launch any Office app due to some background process that got stuck or there might be some glitch in the system. Thus, the first thing you can do to resolve the error is simply restarting your computer. Once you’ve restarted your computer, open the Office app again or you could also try to sign in back with your Microsoft account that’s connected to Office. If you’re not quite sure which account you were using, you can follow these steps:

• Open any Office app.
• Then click on File and look for your name located in the top-right portion.
• Now click on it. This will display the email or Microsoft account that’s related to Office.

Option 2 – Try repairing Office from Apps and Features

Since Windows 10 offers some repair features that could replace some of the core files with the original files, you can take advantage of such a feature to fix the “Something went wrong, We couldn’t start your program” error when opening any Office app.

• Open Windows settings and click the Apps and Features option.
• Next, scroll down until you see the Microsoft Office installation option. Select it and click on Modify.
• This will open a window and from there, select Quick Repair or Online Repair and click on the Repair button.

Note: When you choose to repair, you might be given two options which depend on how Microsoft Office was installed. For instance, it was installed via Web Installer or Offline Installer (MSI-based). In Web Installer, select Online Repair > Repair when you’re prompted on how you would like to repair Office. While in MSI-based, you have to select Repair under “Change your installation” and then click on Continue. The repair process makes sure that the app data remains untouched.

Option 3 – Try to uninstall and reinstall Office

If neither of the two given options above worked, then you might want to uninstall Office and reinstall it. All you have to do is download the Microsoft Office Uninstall tool from the official site of Microsoft and run it. This will remove any incomplete Office installation as well as unwanted files. It will also get rid of all the Office apps and settings on your computer.

BSOD or Blue Screen of Death errors are one of the toughest issues you can encounter in Windows 10 as well as the hardest ones to resolve as they simply shut the system down or restart it abruptly and claims that it isn’t possible to boot Windows again. One of the difficult BSOD errors is the Machine Check Exception BSOD error. The reason why it is hard to fix is that in most cases, it occurs soon after Windows loads which gives users little to no time in resolving it. To make things worse, the system also freezes right before it displays the blue screen error and shuts the system down. Usually, the Machine Check Exception Stop error occurs due to the failure or overstressing of the hardware components. And in the case of almost all Blue Screen of Death errors, the issue usually has something to do with the drivers. So if you frequently see this BSOD error from time to time, now’s the time to act on it by following the solutions given in this post.

Option 1 – Update the Device drivers

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. Look for the device driver you and then select either “Update driver” or “Uninstall device”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• If you have chosen to uninstall the driver, follow the screen options to complete the process and then restart your PC.
• Connect the device and Scan for hardware changes – you can see this option under Device Manager > Action.

Option 2 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that can be found on the Settings Troubleshooters page. To use it, refer to these steps:

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

Option 3 – Try running the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be causing the Machine Check Exception BSOD error. 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.

Option 4 – Run the Startup Repair

In the Blue Screen where the Machine Check Exception error is displayed, tap the F8 key to go to the Startup Settings where you can find Startup Repair and then run it. Note that this is a must-try option especially if you are unable to start your computer and if you can use your computer for a few moments.

Option 5 – Run the DISM tool

There are cases when the Machine Check Exception error is caused by the Windows System Image so you need to repair it using the DISM or Deployment Imaging and Servicing Management tool. The DISM tool is another command-line tool in the Windows operating system that could help users fix various corrupted system files. To use it, follow these steps:

• Open the Command Prompt as admin.
• Then type in this command: Dism /Online /CheckHealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 6 – Try resetting the BIOS

If you have made some modifications in the BIOS that might have caused this error, you have to revert those changes to resolve the issue. On the other hand, if you have made a couple of changes and you do not remember which is which, you might have to reset the BIOS.

Option 7 – Try resetting Windows 10

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