Fix Realtek HD audio driver issue

The third time is charm saying goes but not when we are talking about Microsoft. Print spooler is again in focus, in a bad way. This is the third print spooler vulnerability to emerge in just five weeks. While a critical flaw was originally identified and patched in June, a similar flaw came to light shortly after and was subsequently patched (with mixed success). Microsoft is once again advising its customers to disable Windows print spooler after a new vulnerability that allows hackers to execute malicious code on machines has emerged. While a patch fixing the flaw will be released in due course, the most effective workaround currently on the table is to stop and disable the print spooler service entirely.

"An elevation of privilege vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights."

Stop this service right away or you are risking a potential attack.

1. Press ⊞ WINDOWS + X to open the hidden menu
2. Click on Power Shell (admin)
3. In Power Shell type in the following command to check if spool service is running: Get-Service -Name Spooler followed by ENTER
4. If spooler service is running type in the next command to stop it: Stop-Service -Name Spooler –Force and press ENTER
5. Then follow with this command to disable it at startup: Set-Service -Name Spooler -StartupType Disabled followed with ENTER

That’s it, we hope a patch will come soon for all the people that are using network printing and indeed need this service running in order to do work.

After so many years World of Warcraft is still among the most played MMORPG games in the world. It is still constantly updated with new content and tweak graphically in order to be relevant and fresh. But even the best or most popular ones can still have some minor issues and bugs from time to time. CAS System Was Unable to Initialize is the error that was reported lately by WOW players all around the globe and it happens in multiple Windows systems. In this guide, we will take with this issue and provide you with solutions on how to fix it so you can get back to enjoying the game itself.

1. 1. Repair WOW

      In battle.NET launcher select WOW and click on Options Click on Scan and Repair Let the process finish and then launch the game again

   2. Clean Windows registry

      Windows cleaning registry operation is a complex task and we will not cover each possible scenario here, instead of trying manually to find issues and clean registry download and install third party registry cleaner software.

   3. Run WOW with command line argument

      One of the solutions for this particular error is to run WOW with a specific command line switch: Run battle.NET client as administrator by right-clicking on it and choosing run as administrator If you are not signed in, sign in now Click on World of Warcraft to select it Click on options Click on Game settings Check the box associated with Additional command-line arguments When the box is selected you should've able to add inline argument or switch, add -uid wow_engb and confirm Run World of Warcraft

   4. Enable Secondary logon service inside Windows

      It was reported that enabling this service can fix the issue. Press ⊞ WINDOWS + R to open the run dialog Inside run dialog type in services.msc to open services windows Locate the Secondary Logon service Right-click on Properties from the context menu Inside the properties, screen click on the general tab Change the Startup type to Automatic and hit Apply to save the changes Run World of Warcraft

   5. Delete the cache folder

      Both indices and cache folder needs to be deleted in order to reset corrupted data. Make sure that both World of Warcraft and battle.NET are fully closed For this step to work, you will need to go into the folder where you have installed the World of Warcraft game. By default this is in C:/Program Files/World of Warcraft/ but if you have used another folder go there via file explorer. Once you are inside the folder locate the indices folder and delete it After that locate and delete the cache folder as well Restart your computer and start battle.NET

   6. Remove read-only attribute from WoW folder

      Another reason for CAS System Was Unable to Initialize error is because the World of Warcraft folder has been set to read-only and since the client does not have write privileges it will throw this error. To remove the read-only attribute from the folder go to your World of Warcraft installation folder but do not enter it Right-click on it instead and choose properties Under properties uncheck the read-only box and confirm. Run World of Warcraft

As you know, all the web browsers come with the support of auto-updates which include both Google Chrome and Mozilla Firefox. However, with these updates, the browser comes with the support of a new web APIs and better rendering. Although there could be a lot of problems that may arise due to these updates. These problems consist of depreciation of features, incompatibility with some websites, to name a few. It includes incompatibility with some websites, depreciation of features, and more. This might push someone to stop the auto-updates of these web browsers. So, in this guide, we will be checking out how to stop auto-update in Google Chrome and Mozilla Firefox on Windows 10. Thus, if you want to be rid of these issues, then you can disable the Chrome & Firefox auto-update and you can do that by either using the Windows Services Manager and the System Configuration utility.

Option 1 – Disable Chrome & Firefox auto-update via Windows Services Manager

The first thing you can do to disable the Chrome auto-update is through the Windows Services Manager. To do so, follow these steps:

• First, tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• After that, you will see a list of services and from there, look for the Google Update Services (gupdate) and Google Update Service (gupdatem).
• Once you find these services, right-click on each one of them and select Properties and then make sure that the Service Status is set to be Stopped.
• You should also select the Startup Type to Disabled and click on the Apply and OK buttons.
• Now restart your computer. This should stop the automatic update of the Chrome browser.

Option 2 – Disable Chrome & Firefox auto-update via System Configuration utility or MSConfig

• Tap the Win + R keys to open the Run utility and type “msconfig” in the field and tap Enter to open the System Configuration.
• After that, go to the Services tab and uncheck the two entries, namely Google Update Service (gupdate) and Google Update Service (gupdatem).
• Next, click on the Apply and OK buttons to save the changes made.
• Restart your computer.

Note: Now that you’ve stopped the auto-update in Firefox, it’s time for you to stop the auto-update in Mozilla Firefox. To get started, follow the steps below.

• Open the Mozilla Firefox browser and click on the hamburger menu located on the top-right portion of the screen.
• After that, select Options and under the General panel and then go to the Firefox Updates section.
• Next, click on the radio button for updates but select the option to let you install them.
• You also have to uncheck the options named “Use a background service to install updates” and “Automatically update search engines”.
• Once done, restart the Firefox browser. This should stop the automatic update.

Fatal error C0000034 happens during the installation of the Windows update and if you are one of the unlucky users who sadly run into this, keep reading as we will provide solutions to this error and how to get around it. Start from point 1 to the bottom and hopefully you will have your PC back into working order in no time.

1. Run Windows Update troubleshooter

   Usually, a built-in Windows troubleshooter can solve issues painlessly and fast, my advice is to try this as the first option, it is a simple and clean solution worth trying and in 90% it solves the issue all by itself.

2. Do a clean boot

   Using task manager, remove all nonessential applications and services from starting up, reboot your computer, and once it is cleanly booted try re-running the update process again, if the issue was running the application this time everything will work since the problematic application is not running.

3. Reset Windows update components to the default

   This solution requires you to use the Reset Windows Update Agent Tool to reset Windows Update components to default or use this PowerShell script to reset Windows Update Client. You can also manually reset each Windows Update component to default and then re-run the update.

4. Disable firewall and antivirus

   Altho not likely it is still a possibility that some firewalls and antivirus can detect windows updates as malicious software and cut them off. If everything else failed, disable the firewall and your PC protection and when it is fully disabled try updating.

5. Do automatic startup repair

   This should be the last thing to do but if everything else failed, do it. Perform Windows 10 Startup Repair. Once the startup repair completes successfully, you can re-run the update. The update should install without errors.

As of the time of writing this article you no longer need or are required to have a password if you plan to log in to your Microsoft account. Microsoft explored various options for account security and came to the conclusion that passwords are obsolete. Microsoft is letting you access your account through the Microsoft Authenticator app, Windows Hello, a security key, SMS verification, or email verification code. All of these methods are way better in terms of security than passwords.

How to turn these features on?

To get rid of your Microsoft password, the process is simple. You simply need to go to your Microsoft account, click “advanced security options,” then “enable passwordless accounts” under the Additional security section.

One of the most useful and powerful built-in utility in Windows 10 is the DISM tool. This tool can be used with the Command Prompt command line as well as for other purposes. However, it is not without flaws and there are times when you may encounter some issues while using it. One of the problems you can get while using the DISM tool is the following error:

“The scratch directory size might be insufficient to perform this operation”

This kind of error in DISM occurs when the DISM command is executed from the Windows Recovery Environment due to the limited size permissions of a delivery where the operating is being performed. To fix this DISM error, you need to follow the instructions laid out below. Step 1: First, tap the Win + R keys to open the Run utility and then type “cmd” in the field and tap Enter to open Command Prompt. Step 2: Next, you have to specify a scratch directory that contains the Windows folder and to do that, you can either use the DIR command or the BCEDIT command. So in the elevated command prompt type and enter “dir” or “bcedit”. Step 3: After that, you will see a list of folders inside the C: partition. Now you have to create a folder named “scratch” inside the partition. To do so, execute the following command:

mkdir C:Scratch

Note: The command you just entered will create a directory inside the root of the C: partition named Scratch. Step 4: Now that you’ve created the Scratch folder, note that each time you run any of the DISM commands, you have to enter the following code snippet in them:

/ScratchDir:C:Scratch

 Note: For instance, if you are using the DISM tool to repair the offline Windows image, instead of executing the “Dism /Online /Cleanup-Image /RestoreHealth” command, you now have to execute the “DISM /Image:C: /ScratchDir:C: Scratch /Cleanup-Image /Restorehealth” command. And if you want to remove a selected installed update package, you can use the “DISM /image:C: /ScratchDir:C:Scratch /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e75~amd64~~16299.196.4.9” command. Keep in mind that the mentioned package is only an example. And lastly, you also have to replace the drive letter in the new code snippet when you execute the commands given above.

DRIVER_IRQL_NOT_LESS_OR_EQUAL will cause your computer to go to the blue screen of death but do not worry there are solutions around this and we are here to instruct you on how to solve this.

1.  Uninstall and install network drivers

   DRIVER_IRQL_NOT_LESS_OR_EQUAL is most commonly tied to bad network drivers, whatever that be a corruption of the driver files or their incompatibility. So first thing is to check if this is the case. Press ⊞ WINDOWS + X to open the hidden menu in Windows and click on Device Manager. In the Device Manager expand Network adapters, choose adapter, right-click on it and choose Uninstall. Install latest driver or reboot so Windows will install the driver automatically

2. Update driver

   If you do not want to reinstall the driver or you are unable to for whatever reason updating the driver might do the trick. To update driver: Press ⊞ WINDOWS + X to open the hidden menu in Windows and click on Device Manager. In the Device Manager expand Network adapters, choose adapter, right-click on it and choose Update Driver.

3. Fix via Command prompt

   If both of the beforementioned solutions fail, try running the command prompt and fix the issue from there. Press ⊞ WINDOWS + X to open the hidden menu in Windows and click on Command Prompt (administrator) In command prompt type next line and press ENTERDEL /F /S /Q /A “C:\Windows\System32\drivers\mfewfpk.sys Reboot the system

4. Scan your PC for malware

   Sometimes corruption in the system is caused by malware, Scan your system for malware, viruses, etc.

5. Check connections or other hardware issues

   If all methods fail, open your PC case and check to see if connections everywhere are properly connected and tight. Clean your PC and turn it back ON

6. Use system restore

   If anything fails, use Windows system restore and bring back computer into a state where everything was working fine.

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

Option 1 – Check for certain Windows Services

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

Option 2 – Try resetting the Winsock drivers

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

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

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

Option 3 – Try running System File Checker or SFC scan

You could also run System File Checker or SFC scan to fix the BSOD error. It is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

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

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

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

• Reboot your PC.

As you know, Windows Updates are essential for your operating system as it keeps it protected from potential threats, fixes bugs and improves your experience in using Windows 10. However, there are instances when Windows Updates also cause errors and one of them is the Windows Update Error 0x8024000B. One of the causes of this particular Windows Update error is that Windows was not able to read the Update Manifest file which is needed to install the Windows Updates. This means that the operation was canceled by either the service or the user. On the other hand, this error could also occur if you are not able to filter the results. When you encounter this error, you will see an error message that says, “WU_E_CALL_CANCELLED: Operation was canceled”. This indicates that the operation was canceled by the operating system itself. To resolve the Windows Update Error 0x8024000B, here are some suggestions you need to check out.

Option 1 – Try to run the Cleanup (Decline) Superseded updates PowerShell script

The first thing you can do to fix the Windows Update Error 0x8024000B is to run the Cleanup (Decline) Superseded updates PowerShell script. This is actually an easy fix since all you have to do is download and run it from the Microsoft Technet site. Once you’re done downloading and running the file, restart your computer and see if the error is fixed or not.

Option 2 – Try to rename the Spupdsvc.exe file

If the first option didn’t work, you can try renaming the Spupdsvc.exe file which is one of the reasons why you’re getting the Windows Update Error 0x8024000B.

• First, tap the Win + R keys to launch the Run utility.
• Next, type the following command and hit Enter to execute it in cmd:

 /c ren %systemroot%System32Spupdsvc.exe Spupdsvc.old

• The command you entered will rename the troublesome “Spupdsvc(.)exe” file to “Spupdsvc(.)old”.
• Now restart your computer after the command has been executed.

Option 3 – Try to restart various Windows Update-related services and components

You could also try to restart some Windows Update-related services to resolve the Windows Update error. Refer to the following steps to do so:

• Tap the Win + X key combination and select Command Prompt (Admin) to open Command Prompt with admin privileges.
• After opening Command Prompt, copy and paste each one of the commands listed below one by one and tap Enter right after you enter each command.
  • net stop wuauserv
  • net stop bits
  • net stop appidsvc
  • ren %systemroot%SoftwareDistribution SoftwareDistribution.bak
  • ren %systemroot%system32catroot2 catroot2.bak
• Once you’ve entered all the commands given above, they will stop all the Windows Update services that are running on your computer as well as clear the SoftwareDistribution folder, and reset the Catroot2 folder. Now you have to start all these Windows Update services you’ve just stopped by executing the following commands:
  • net start wuauserv
  • net start bits
  • net start appidsvc
  • net start cryptsvc
• After that, restart your computer and try to run the setup again, and see if the error is now fixed.

Option 4 – Try to run the Windows Update Troubleshooter

You should also try to run the built-in Windows Update troubleshooter as it could help you resolve the Windows Update Error 0x8024000B. To run it refer to these steps:

• Go to Settings and then click on Windows Update from the given menu.
• Next, click on the Troubleshoot option and select Windows Update from the given options to run the Windows Update troubleshooter.
• After that, follow the next on-screen instructions and wait until the process is completed, and check if the Windows Update Error 0x8024000B is fixed or not.

If you’ve tried resetting your Windows 10 computer using the Reset This PC option in order to restore your computer’s factory settings and the process suddenly fails for some reason and you got an error message instead stating, “There was a problem resetting your PC, No changes were made on your Windows 10 computer”, then this post might help you resolve the problem. Carefully follow each one of the options given below to resolve the “There was a problem resetting your PC error on Windows 10.

Option 1 – Try renaming the System and Software hive

• If you’re still able to boot to the desktop of your Windows 10 PC, open an elevated Command Prompt from the WinX menu.
• Now use the CD command and change the directory to Windows\System32\config folder. Simply type in the following command and hit Enter:

cd %windir%system32config

• After that, you have to rename the System and Software registry hives to “System.001” and “Software.001”, respectively. To do that, just type each one of the following commands and hit Enter after you type each of them.
  • ren system system.001
  • ren software software.001

On the other hand, if your Windows 10 PC isn’t able to boot to the desktop, you can just access Command Prompt from the Advanced Startup options or you can also boot into Sage Mode and open Command Prompt from there and then run the given commands above. Note: If you only want to use the Refresh your PC option, you must only rename System hive and not Software hive. On the other hand, if the Software hive is really corrupted, you might not be able to use the Refresh your PC option in such a case. Thus, you really need to rename the Software hive as well. Once you’ve renamed the Software hive, you won’t be able to use the Refresh your PC option but only the Reset your PC option.

• Type “exit” to close the Command Prompt and then restart your PC and try resetting your PC again.

Option 2 – Try to disable and re-enable the Windows Recovery Environment

If the first option didn’t help, you can try disabling the Windows Recovery Environment and then enable it back again. To configure a Windows Recovery Environment or Windows RE boot image and recovery options, you have to use the REAgentC.exe tool.

• Tap the Win + S key and type “REAgentC.exe” to open the REAgentC.exe tool.
• After that, type the following command and hit Enter to disable the Windows RE:

reagentc /disable

• After disabling the Windows RE, you need to enable it back by typing the following command:

reagentc /enable

Option 3 – Try to boot the USB recovery drive

If the two previous options failed, you need to try another workaround which is to boot to the USB recovery drive > Troubleshoot > Recover from a drive. From there, follow the on-screen instructions and you should be good to go.