Windows Update Keeps Turning Off in Windows

Lately, Microsoft has trying to fix Print Nightmare with various methods and patches. The last patch has seemingly fixed Print Nightmare but it has broken the Alt-tab key combination. It has been reported that the latest patch has broken famous key combinations for quickly switching from window to window. It seems that combination is not working or it is switching to desktop, even going to blank screen if switching from the full-screen game.

Fixing the issue

Luckily this issue is easily fixable. The first and easier fix for this issue is surprising to turn off the news and info widget, right-click on it and choose News and interests and then click on turn off. The second solution would be to uninstall the update. Go to Settings, then to Update & Security, and from there view Update History and remove the update.

As you know, one of the most highlighted features of Windows 10 is Windows Updates. It was offered to the customers as a service rather than a product with the release of Windows 10 under the scenario of Software as a Service which led to Windows Updates being set by default on Windows 10 and without an option for any users to disable it. Although not all users are happy with what Microsoft did, this is an ultimate step towards the greater good of all its customers since Windows Updates helps users in keeping their computers secured against all kinds of threats as well as provide them with the greatest and latest updates from Microsoft. So if you are one of those users who approved of the Windows Updates service, then read on as this post will guide you in running Windows Updates from Command Line either via Command Prompt or Windows PowerShell. For the complete set of instructions, refer to the options given below.

Option 1 – Run Windows Update via Command Prompt

Command Prompt in the Windows operating system exists for a very long time now compared to the comparatively new Windows PowerShell. That’s why it has similar capabilities to run Windows Updates. However, the highlighting point here is that you don’t have to download any module for Windows Updates. To get started running Windows Updates using Command Prompt, refer to the steps below.

• First, type “cmd” in the Cortana search box, and from the search results, right-click on Command Prompt and select the Run as Administrator option to open it with Administrator privileges.
• If a User Account or UAC prompt appears, just click on Yes to proceed.
• Next, type in the commands listed below, and don’t forget to tap Enter right after you type each one of them.
  • UsoClient StartScan – use this command to start checking for updates.
  • UsoClient StartDownload – use this command to start downloading updates.
  • UsoClient StartInstall – use this command to start installing the downloaded updates.
  • UsoClient RestartDevice – use this command to restart your computer after you install.
  • UsoClient ScanInstallWait – use this command to check, download and install updates.

Note: Keep in mind that the commands in Command Prompt listed above are only meant for Windows 10. On the other hand, if you are using an older Windows version, you can try using the following commands instead:

• wuauclt /detectnow – use this command to start checking for updates.
• wuauclt /updatenow – use this command to start installing the updates detected.
• wuauclt /detectnow /updatenow – use this command to check, download and install updates.

Option 2 – Run Windows Updates via Windows PowerShell

If you run Windows Updates in the Windows PowerShell, it will require you to install the Windows Update module manually. Hence, you have to get the Windows Updates downloaded and install Windows Updates.

• Search for PowerShell in the Cortana search box and then run it with administrator privileges.
• Once you’ve opened the Windows PowerShell, type the following command and hit Enter.
  • Install-Module PSWindowsUpdate – use this command to install the Windows Update module for Windows PowerShell.
  • Get-WindowsUpdate – use this command to connect to the servers of Windows Update and download the updates if found.
  • Install-WindowsUpdate – use this command to install the Windows Updates you’ve downloaded to your computer.

Among other things and innovations, Windows 11 brings to the table is the game mode. The game mode is a system designed to release some resources and optimize your system when Windows 11 detects that you are playing games. It also turns off automatic updates while the game is active. The game mode is active at all times and usually, everything works great but in some instances, it can sadly cause some performance issues. If you are one of these unlucky people where game mode is not working as supposed to do, don’t panic, we have a quick guide for you on how to turn it off.

1. Press ⊞ WINDOWS + I to open settings
2. Inside click on Gaming
3. Select Game mode
4. Click switch beside Game mode to turn it off
5. Close settings

Everything will be automatically saved and applied and you should not have any issues from now on. If for any reason you wish to turn game mode back ON, just follow the same steps and turn the switch to ON.

Despite popular belief, there are a lot of users running Linux OS. Linux offers great security and working environment and 96.3% of the world's top 1 million servers run on Linux. 90% of all cloud infrastructure operates on Linux and practically all the best cloud hosts use it. But gaming on Linux is limited, enter Steam proton a Valve’s gaming solution.

What is Steam proton?

Proton is a WINE fork with some extra capabilities, to play games and run applications not native and not made to run natively under Linux OS. It is supposed to bridge the Gaming issues for PC users and let them more freedom in choosing an operating system to game on.

Find out if your game supports Proton

Although there are a lot of titles that nowadays run natively on Linux some will still need proton in order to run at all and sadly some of them will not be able to run on Linux even via proton but seeing how Valve is busy and it is trying to push its ideas and technology slowly this gap is closing. In order to see how the game you want to play performs and behaves on Linux and proton environment visit https://www.protondb.com/ and find out. As soon as the site loads you will be greeted with statistics and a search option to find out the status of the desired game with one of the given statuses: Borked, Bronze, Silver, Gold, Platinum, and Native. As you probably guessed native means that the game will work on Linux out of the box and borked will probably not work at all. Platinum and gold status means that game will run on proton without any input or tweaks from the user while silver and bronze means that it will work but might need some tweaks in order to make it work.

How to get Steam proton?

In order to run games under proton inside Linux, you will need firstly a Steam client which luckily works naturally on Linux. Unlocking/activating Steam Proton on your Linux-based system is easy. Just head over to Steam > Settings > Steam Play and toggle the option “Enable Steam Play for Supported Titles”. Valve has tested and fixed some Steam titles and you will now be able to play those titles. However, if you wish to go even further beyond, and play titles that even Valve has not tested, toggle the option “Enable Steam Play for all titles”.

Conclusion

Even we are not there yet, native gaming on Linux is gaining a foothold each day. Will Steam’s OS with proton technology be one that will turn the tide from Windows or some other tech we cannot tell but one thing is for sure, more choices mean better products so I am hopeful for a bright future.

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 0x0000001e is when you start the Windows XP Setup and you see a message which says something like: STOP: 0x0000001E (0x80000003, 0xBFC0304, 0x0000000, 0x0000001)

Solution

Error Causes

You are most likely to face this error if you restart your PC while the Windows Setup is still under process and yet to complete. Other causes of this error include any of the following conditions:

1. The drive on which you are installing Windows has insufficient disk space to accommodate the installation.
2. An incompatible or outdated third-party driver (or more) is installed on your PC which is conflicting with the installation. For instance, this could be a problematic video driver.
3. The system BIOS has incompatibilities with the installation.

Further Information and Manual Repair

This error is also called the “Bug check code”. The STOP 0x1E signifies that there was an unknown or illegal processor instruction detected by the Windows XP kernel. You will see the exception address which shows up to indicate the root of the problem which is usually a driver or faulty hardware. You should note this address down as well as the link date of the faulty driver or image which includes it. If at any point it becomes impossible for you to handle and you end up contacting the Windows support center to help you out with the process then this information will help you out in making things a lot easier while the support team tries to troubleshoot the problem. The parameters included in the STOP 0x1E error message are the following:

1. is the exception code which couldn’t be handled.
2. shows the module’s address where the exception took place.
3. signifies the exception’s parameter 0.
4. represents the exception’s parameter 1.

You can use this information which usually is provided in error 0x0000001e message to pinpoint the root cause of the problem and troubleshoot it. In order to fix this error, you need to follow either one of the following procedures as needed according to your situation.

Clean Up Your Disk

If your disk doesn’t have ample space to accommodate the installation then you should free up some of the space on your disk to make sure the Windows can be installed on it. You can also reinstall the Windows on another disk that has sufficient space.

Get Rid of the Third Party Driver

If the error 0x0000001e message gives you the name of the driver due to which the installation process is being halted, then get rid of that driver by disabling it or removing it. If the problem is resolved by this then you should contact the manufacturer of the third-party driver and ask them about any newer versions of the driver that wouldn’t conflict with the installation of Windows.

Upgrade System BIOS

Upgrading your system BIOS is something that you can’t do on your own. You will need to find out more about how you can upgrade. For this, you should contact either your PC’s manufacturer or your motherboard’s manufacturer. If nothing else works, you can always make use of the Microsoft Debugging Tools which will provide you ample information about the error message. You will find the Debugging Tools and further information about them including the downloading and installation process on Microsoft’s website.

As you know, each one of the Windows 10 versions is priced differently and one of the considered more expensive compared to the Windows 10 Home version is the Windows10 Pro. The good thing is, Microsoft allows its users to upgrade from the Windows 10 Home version to the Windows 10 Pro version at a reasonable cost instead of buying the entire license again. However, upgrading your Windows 10 computer is not always that easy and you might encounter some errors along the way. One of the reported errors you could encounter is an error message that says, “Something happened, and we couldn’t start the upgrade”. This kind of problem is due to the problems with the Microsoft Store or the key authorization and to fix it, there are several options you can check out. You can try to run the built-in troubleshooters such as the Windows Update troubleshooter, Windows Store Apps troubleshooter, or Microsoft Accounts troubleshooter. You could also try to reset the Windows Store cache or re-register the Windows Store app. For more details, refer to each one of the given options below.

Option 1 – Try to run the Microsoft Accounts troubleshooter

Since the Microsoft Accounts troubleshooter is not built-in into the Windows operating system, you can download this troubleshooter by clicking on this link.

Option 2 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “Something happened, and we couldn’t start the upgrade” error. 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. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the problem in Microsoft Store. This is a great built-in tool from Microsoft that helps users fix any app issues. To use the Windows Store Apps Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• Under the Troubleshoot section, on your left-hand side, scroll down to find Window Store Apps.
• Then click on the Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 4 – Try to reset the Microsoft Store cache

As you know, like any other apps, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 5 – Try to re-register the Microsoft Store app via Windows PowerShell

• Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

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

Option 6 – Try contacting Microsoft

If none of the options worked, you might also want to contact Microsoft for further assistance in fixing the error.

If you’re having some problem browsing multiple websites on the Firefox browser on your Windows 10 computer, then this post might be of help. One of the most common problems you could encounter in Firefox is mostly related to HTTPS and one of them is the MOZILLA PKIX ERROR MITM DETECTED or ERROR SELF SIGNED CERT or SEC ERROR UNKNOWN ISSUER error which means that Firefox was unable to trust certificates issued on secured websites. If you encounter the MOZILLA_PKIX_ERROR_MITM_DETECTED error in Firefox, this indicates that something in your network or system is interrupting your connection and injecting certificates and when that happens, Firefox won’t trust it. In such cases, one of the culprits is malware. Malware will try to replace a legitimate certificate with its certificate. Another cause is security software where it keeps a tab on a secure connection and creates a false positive, for instance:

“In Microsoft Windows accounts protected by Family Safety settings, secure connections on popular websites like Google, Facebook and YouTube might be intercepted and their certificates replaced by a certificate issued by Microsoft in order to filter and record search activity.”

And if you are connected to a corporate network, there might be a monitoring/filtering product that could be replacing certificates. Moreover, there are also users who reported getting this issue when they use the Nightly version of Firefox. And if that’s the case, you have to try accessing secure websites using only the stable build especially when it comes to payments. However, if you are not doing that, then here are some options you need to check out.

Option 1 – Try turning off HTTPS Scanning on your security and antivirus programs

Each security-based software has a security option that allows you to turn off the HTTPS scanning functionality. They may be available under different names such as HTTPS Scanning, Scan SSL, Show safe result, Do not scan encrypted connections, etc. Find what is applicable for your security or antivirus software and then try turning it off temporarily and see if it helps in fixing the MOZILLA_PKIX_ERROR_MITM_DETECTED error in Firefox.

Option 2 – Try to disable security.enterprise_roots.enabled

The next thing you can do if the first option didn’t work is to disable security.enterprise_roots.enabled which is an HTTPS certificate check on Firefox. Note that this is not recommended but you have to at least try in order to fix the error.

• Open Firefox and then type “about: config” in the Firefox address bar and hit Enter.
• After that, if an info message appears, confirm it.
• Next, search for the security.enterprise_roots.enabled preference and once you found it, double click on it.
• Then change its value to true and restart the Firefox browser once. This will import all the custom certificates from the other security software into Firefox. As a result, it will make sure to mark those sources as trusted and you won’t get the MOZILLA_PKIX_ERROR_MITM_DETECTED error.

System image backup error 0x807800A1 & 0x800423F3 appears when you are trying to create a system image backup and the operation fails to do so. If you’re faced with any of these error codes, try our recommended solutions in the order presented below and resolve the issue.

Check Volume Shadow Copy & Software Protection Services

To restart the Volume Shadow Copy Service (VSS) on Windows 10, do the following:

• Press ⊞ Windows + X to bring up the Windows menu.
• Click on command prompt (admin)
• In the command prompt window, type the commands below and hit Enter after each line:

net stop vss net start vss

Once the commands execute successfully, try the system image backup again. The operation should complete successfully. You need to also check if the Software Protection Service is disabled. If it is, then Start it and ensure that it is set to default which is Automatic (Delayed Started).

Create System Image using PowerShell

Command lines are less prone to errors provided the syntax is correct, unlike GUIs that can suffer a glitch every now and then. To create a system image with PowerShell do the following:

1. Open the Windows PowerShell as administrator. To create a System Image in Windows 10 using PowerShell, you will have to run the Wbadmin command.
2. Inside the Powershell window type, then press Enter: wbadmin start backup-backup target: E:-include: C:-quiet-allCritical E: is the target drive where you’re going to save the system image, and C: is the system root drive where Windows is currently installed
3. To extract the created system image, starting over from Windows 10 USB installation media, select advanced startup or open run and type: C: \ Windows \ System32 \ Shutdown.exe / r / o

Use third-party imaging software

If the previous two solutions have not managed to solve the issue there is always an option to use a third-party imaging solution. There are free open source and buying options offering various advantages each. Find out which one works best for you and use it.

It has been some time since the release of Diablo 2 resurrected and overall reception was pretty good. People are enjoying the old classic game in hi-def. resolution and with new and improved visuals. Sadly some server issues are present still until this day and somewhat spoil the experience for players. The greatest lag and server crashes are pinpointed to game-creating events. When a player creates a new online game, the server needs to pull a lot of details from the database and make a game, due to some legacy code present this process takes some time and it is demanding a bit on the server-side, and although code was optimized to cater to more modern approach some legacy code still remains. Another thing that was spotted to affect performance itself is player behavior, to be more specific, modern gamer behavior. Where players find good builds and runs on the internet and then go to farm-specific areas or bosses for loot or experience points, which in return boils down to making plenty and short runs that are made by creating games and after run eliminating them. Now pair that with the previous statement about legacy server and database code and you can add 1 and 1 and see how this might be an issue. A lot of short games over legacy code are placing games in a state it was not designed for back in 2001 and therefore we have issues. Sadly solutions without completely rewriting the whole code are not very promising and they include rate limiting, which will prevent players to create many games in succession in a short period of time and maybe even login queues to drop a load on servers. Blizzard reached to people in the whole company, even old diablo 2 developers to ask for advice and they say that they are working on solutions so they could lift limitations and have everything running fine.