How to Fix the Error Code 28

Originally Microsoft has imagined its widgets menu as Microsoft-only widgets but it seems that they have changed their mind. Due to the latest leak, it seems that Microsoft will open the widgets menu to 3^rd party developers as well but at launch, it will be only official widgets. It was hinted that later widgets menu will be open to developers who want to bring their own stuff into it. Distribution, date, and technology that will need to be used in order to create your widget have not been discussed nor leaked at a given time but in some way, I am very glad that at least some customization will be in Windows 11. It is funny and amusing how some things that were in Windows Vista are getting back like glass design, round corners, and widgets. Let’s just hope Windows 11 will be a better Windows than Vista was.

A PC that turns on by itself every so often can get quite annoying. Many users have faced this problem countless times. There are lots of possible reasons why your Windows 10 PC turns on by itself, wakes up from sleep, standby, or even when it’s shut down. To find out what exactly woke your computer, simply open Command Prompt as admin and type the following command:

powercfg –lastwake

Once you enter the command given above, it will show you the last device that woke your PC up. After that, you need to type in the next command:

powercfg –devicequery wake_armed

After entering the command, it will show you a list of all the devices that could wake your PC up. The goal in running these commands is to understand the reason what’s really causing your PC to turn on and see the reason is on the hardware level or not. Here are a couple of options you can try if your Windows 10 PC turns on by itself.

Option 1 – Try disabling Fast Startup

As you know, Windows 10 comes with a mode called Fast Startup which does not turn off the computer in the usual manner. This mode keeps your computer in a mixed state so that when you turn it on again, it will be a lot faster. However, as useful as this feature appear to be, some security experts find this an issue, for numerous reasons – for one, it can turn on your Windows 10 PC by itself. Thus, you need to disable this feature to fix the problem.

Option 2 – You need to stop the Task Scheduler from waking up your computer

There are times when the issue has something more to do with the software than hardware. It could be that you are using a Scheduled Task to get some work done on your computer at a particular time of the day or many times a day. That’s why if you really are using Task Scheduler, you need to change the Power settings of Windows to make sure that it ignores those tasks rather than deleting them instead when your computer is either on Hybrid or Standby mode.

• Open the Power Options and then click on “Change Plan Settings”.
• After that, make sure to choose the correct power plan and then select the “Change advanced power settings” option.
• Next, look for the Sleep tree and expand it to view the “Allow Wake Timers” option and then disable it. Disabling this option will make sure that none of the program that could wake your PC up when it’s either on shutdown or sleep mode. However, this only applies to laptops.

Option 3 – Try to disable Automatic Restart

There are instances when the computer crashes and the system restarts itself. This is actually by design – when your computer has been left on standby, the computer will restart and if the program repeats, it will keep on waking your PC up.

• In the Search bar, type in “system”.
• Once it appears from the search results, click on it.
• Next, select Advanced system settings on the left side and then go to the Advanced tab.
• From there, click on Settings under Startup and Recovery.
• Then unmark “Automatically Restart” and click on OK.

Option 4 – Adjust the Power Management option of both the Keyboard and Mouse

As you know, two of the culprits in waking your PC up are the keyboard and the mouse. If they’re slightly moved or hit, your PC turns on. To prevent these two from waking your computer up, you need to make some adjustments to their power management option since they have one. You can disable this option to ensure that they won’t wake your PC up unless you really want it to.

• Tap the Win + X keys and then tap M to open the Device Manager and list all the hardware on your computer. From there, select your keyboard or mouse.
• Next, right-click and then go to Properties and go to the Power Management tab.
• In this tab, uncheck the “Allow this device to wake the computer” box.

Note: Aside from the keyboard and mouse, if you are also using any gaming rig to play games on your computer, then you might have to disable their power options as well as they could also wake your computer. Just make sure that either the keyboard or the mouse has the ability to wake your computer up at the very least as it can be quite inconvenient to tap the Power button every time you want to turn on your computer.

Option 5 – Modify Wake On Lan

The Wake On Lan feature can bring back your computer online if it is connected to a network. This feature is useful especially when a computer wants to communicate or to send data or files to a network computer which should come online only when it’s requested. Wake On Lan is built into the hardware, i.e. network adapter so it is one of the possible reasons why your PC turns on by itself.

• Tap the Win + x keys then hit M to open the Device Manager and then under the Network adapters, look for the one that was listed above. Take note that you must not change anything with the ones that are listed as Miniport.
• Next, right-click and select Properties and then go to Power management and from there, uncheck the “Allow this device to wake up the computer” option. This will ensure that no PC on the network can ever wake your computer up.

Option 6 – Prevent any scheduled Windows Update and Automatic maintenance

It is also possible that the Windows Update has restarted your PC to complete the update. This depends on your active hours or a predefined schedule. AS you know Windows has a built-in Automatic Maintenance mode which wakes the computer up at the scheduled time and performs the system update. This could be one of the possible reasons why your computer turns on by itself. so to prevent any scheduled updates and maintenance, you can simply change the time for Automatic maintenance. How? Follow these steps:

• Open Settings then go to Windows Update and Security >Windows Update and select Active Hours.
• After that, type in “Automatic maintenance” in the search bar to change the time for Automatic maintenance.
• From there, you can adjust the timing or just uncheck the “Allow scheduled maintenance to wake up my computer at the scheduled time” box.

Error Code 1627 - What is it?

Error Code 1627 is a type of HP printer installation error. It usually occurs when you try to install an HP printer on your PC. The error code 1627 pop-up hampers your ability to install an HP printer successfully. This error code is usually displayed in the following format:

Installation Error: Call to Driver Package Install returned error 1627 for package C:ProgramFilersHPHP deskjet 2510 seriesDriver storePipelinehpvplog.inf

Solution

Error Causes

Like every device installed on your PC, printers also need software called drivers to function on Windows Operating System. Although Windows supports several computer devices since many drivers are already installed in Windows but there are some devices that do need additional software to get started and operate smoothly on Windows such as Hewlett-Packard HP printers. Installing a Hewlett-Packard printer driver is slightly more time-consuming and complex than any other driver. Causes for HP printer installation usually include:

• Driver issues
• Bad Registry Keys

Though this is not a fatal error, it is still advisable to fix it right away to avoid inconvenience.

Further Information and Manual Repair

To resolve this error on your PC, you don’t necessarily have to hire a professional and spend hundreds of dollars in repair. The good news is that HP Installation error code 1627 is quite easy to fix. Here are some of the best and proven DIY methods to resolve error code 1627:

Method 1 - Uninstall and then Reinstall HP Printer Driver

HP printer installation errors can occur due to driver issues.  If the driver is not installed properly or is outdated, you will never be able to install an HP printer on your PC successfully. Therefore to solve this issue, first, make sure the driver used for printer installation is up to date. If it is outdated, then update it. On the other hand, if the printer driver is up to date but not installed properly then reinstall it. In both situations, first, you must uninstall the driver. Uninstalling the previous installation will help you clean the system. Once the system is clean you can reinstall the HP drivers again. To uninstall, go to the start menu and then the control panel. Now go to the Add/Remove program option and uninstall the driver. To activate changes, reboot your PC. Now install the updated version again.

Method 2 - Clean the Registry

If the printer software installation fails while updating, then this means the removal of the failed software was not successful. It may not show up in the Control Panel program list. This means the entries of the failed software are still present in the registry of your PC. In this scenario, you need to clean the registry and remove the bad entries from there to successfully install the HP printer driver on your system. Though this can be done manually this can be both time-consuming and slightly challenging if you are not technically sound. Therefore, to remove bad entries from the registry in seconds in just a few clicks download Restoro. This is a user-friendly PC Repair Tool deployed with a powerful registry cleaner. The registry cleaner scans your entire PC, detects and removes all bad entries and files corrupting the registry right away. Once the registry is cleaned, you can try installing the printer driver again. This is most likely to resolve the issue. Click here to download Restoro.

Method 3: Locate and Install the Driver

As was pointed out, you might need to reinstall the printer driver again. Using DriverFIX, you'll be able to automatically update your computer system and install the drivers your computer needs to operate smoothly.

Windows Update Error 0x80071a91, what it is? As you know, Windows Updates are very essential to the operating system since they push with them the important security updates that are crucial to the system. And if a Windows Update is delayed, it can the system vulnerable to potential threats. Thus, this kind of issue must be resolved right away. One of the errors that you can encounter while updating your computer is the Windows Update Error 0x80071a91. The error code 0x80071a91 occurs when the “Transaction support within the specified file system resource manager is not started or was shut down due to an error”. This happens when a service called “File System Resource Manager” or FSRM does not function due to some reason. To fix the Windows Update Error 0x80071a91, here are some suggestions that could help.

Option 1 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update Error 0x80071a91. 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 2 – Disable the antivirus program temporarily

There are times when the antivirus program installed in your computer blocks file access and even disk access. Thus, disabling the antivirus program or any security software installed in your computer is always a good idea you can try when the Windows Update process does not go smoothly. So before you try updating your computer again, make sure to disable the antivirus or security program and once the Windows Update is done, don’t forget to enable the antivirus program back again.

Option 3 – Try resetting the File System Resource Manager

As pointed out earlier, the error 0x80071a91 pops up when the FSRM service suddenly stops working and so resetting this service via Command Prompt might resolve the problem. To do so, follow the steps below.

• In the Windows Search box, type “command prompt” and hit Enter.
• Then right-click on Command Prompt from the related search results and click the “Run as administrator” option.
• After opening Command Prompt as admin, type the following command and hit Enter:

resource setautoreset true C:

• After that, exit Command Prompt and restart your computer and then check if the problem’s fixed by running Windows Update again.

Option 4 – Flush the contents of the SoftwareDistribution folder

You have to stop a couple of services such as BITS, Cryptographic, MSI Installer, and Windows Update Services. And to do that, you need to flush 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. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

• 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 start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution 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

Option 5 – Delete the Common Log File System transaction logs

You might also want to delete the Common Log File System or CLFS transaction logs to fix the Windows Update Error 0x80071a91.

• Open an elevated Command Prompt.
• Then type each of the commands listed below and press Enter after you type each one of them.
  • cd /d %SystemRoot%System32SMIStoreMachine
  • attrib -s -h *
  • del *.blf
  • del *.regtrans-ms
• After you’ve executed the commands given above, restart your computer and try to update Windows 10 again.

Error 1753 - What is it?

Error 1753 is an RPC endpoint mapper error code. This code is typically displayed as "EPT_S_NOT_REGISTERED" or sometimes as the hexadecimal value 0x6D9.  Error 1735 indicates that there are no more endpoints available from the endpoint mapper. To understand this better, basically, RPC is an inter-process communication (IPC) method. This is used by clients and servers for communication purposes. RPC is used by programs to execute programs on a server computer. The perfect example of this is Microsoft Outlook. You communicate with Microsoft Exchange Server using RPC. This enables you to send and receive emails. When you use Microsoft Outlook to send emails, your computer sends a message to the server computer in an obscure coding. The server responds to your computer with another message that contains the results of the executed program. This is all being carried at the backend of the running program. Integral to this is the endpoint. The endpoint includes the name, port, or a group of ports on a computer that is monitored by the server for incoming client requests. This is a network-specific address to be precise. The endpoint mapper is the part of the RPC subsystem that is responsible for dynamically assigning endpoints to the server. When this function fails it leads to error 1753 message display. It shows that RPC service is not available.

Solution

Error Causes

The error code 1753 indicating RPC endpoint mapper service failure is triggered due to multiple reasons. These include:

• Windows registry damage and corruption
• Malfunctioning of the hardware
• Spyware intrusion or viral infections
• Device driver conflicts

Further Information and Manual Repair

This error code may cause a great deal of inconvenience to execute programs that are dependent on the server. It can lower your productivity and performance. To avoid the hassle, it is advisable to repair the error 1753 immediately. The best way to resolve this error 1753 in seconds is to download Restoro. By using this repair tool, you can fix the error right away for free without paying hundreds of dollars to a professional expert. Restoro is a new and innovative PC fixer integrated with an automated algorithm and intuitive technology that enables users to sit back and relax while Restoro runs on the system and detects all PC-related issues in the shortest time. In just a few clicks you can resolve even the mightiest PC issues like the error code 1753 RPC endpoint mapper problem and resume back to the program in no time.

Why Restoro

It is efficient and user-friendly. Restoro can be used by users of all levels so even if this is your first experience using a repair tool, you don’t have to worry. To operate it, you don’t have to be a computer programmer or have sound technical expertise. It is simple and very easy to use. The layout is simple and neat complimented nicely with easy navigation and a sophisticated user interface. Restoro is a high and multi-functional error tool embedded with powerful, performance-driven, and value-adding utilities, all in one. So, whether the error code 1753 is triggered due to a viral infection on your system or registry corruption, you don’t have to look for different tools to resolve the error, simply run Restoro to fix the issue right away. Restoro includes a dynamic registry cleaner that detects all registry issues and wipes out the clutter from the hard disk like junk files, internet history, and invalid entries which is by the way the number cause for registry corruption leading to error 1753. It clears up disk space and RAM and repairs the misconfigured system files and corrupt registry in seconds thus resolving error 1753. Restoro also functions as a system optimizer thus boosting the speed and performance of your PC massively and reducing boot time. In addition to this, it also has a backup feature.  This tool is embedded for safety purposes. This feature enables you to create backup files on your PC before you start system repair. This helps you recover data in the event of data loss during system repair. To get started:

• Click here to download and install Restoro on your system
• After installation, run it to scan for errors like 1753
• Now press the repair tab to resolve

One of the useful things you can use on your laptop is touchpads. They help users in achieving tasks through the gestures and multi-finger tap or touch support it brings in the scope for various shortcuts. However, not all times touchpad brings productivity as it can also encounter some issue every now and then. One of these issues has been reported on a couple of Lenovo laptops that use touchpad drivers from the Alps Pointing Device. According to the reports, an error saying, “Set user settings to driver failed” when they use the touchpad. This type of error on the touchpad usually occurs when a computer boots up and it could be caused by a faulty update on the Alps pointing device driver which is being installed in the background. To fix this error on the touchpad, you could try to disable the Alps pointing device entry from the MSConfig or you could try to get the latest version of the driver or uninstall the driver altogether. Before you proceed with the troubleshooting tips given below, make sure that you create a System Restore point first. Once you have that covered, proceed to the following options.

Option 1 – Try disabling the entry of the Alps pointing device from MSConfig

This first given option was able to fix the problem for many users so to get started, follow these steps:

• In the Start Search box, type “MSConfig” and select System Configuration from the search results.
• Next, go to the Services tab and look for the Alps pointing device entry from the list that appears, and uncheck it.
• Then click the Apply and OK buttons to save the changes made.
• Now restart your computer and see if the error in the touchpad is now fixed.

Option 2 – Try to download and install the latest version of the driver

The next option you can check out to fix the error is to download and install the latest version of the driver from the official website of Lenovo support. Note that an updated version of the touchpad driver will most likely get rid of the error. However, you have to make sure that the version you’re going to get is compatible with your existing Windows version.

Option 3 – Try to uninstall the Alps Pointing device driver

If the first two given options didn’t work, you can try uninstalling the Alps Pointing-device driver instead. You can do this under the Mice and other pointing devices section. After you uninstall the driver, restart your computer and delete the driver’s leftover folder inside this location in File Explorer (C:/Program Files). Once you’re done, restart your computer and check if the error is now gone. Keep in mind that after you’ve uninstalled the driver, any extra configuration features that Lenovo drivers offered before the uninstallation will no longer be available.

Error Code 0x80072EE2 – What is it?

Windows 10 error code 0x80072EE2 usually occurs as a result of a disruption during the upgrade process when users attempt to upgrade their operating system using Windows Update. The disruption may be caused by a loss of Internet connection. Error code 0x80072EE2 may also occur due to problems related to one’s firewall. Common symptoms of this error code include the following:

• Upgrade process fails to complete
• A message box pops up highlighting the presence of error code 0x80072EE2

Solution

Error Causes

Upgrade error codes like error code 0x80072EE2 usually occur when disruptions or problems related to system files, or third-party apps prevent Windows Update from completing an upgrade. In the case of error code 0x80072EE2, the most likely cause is a bad Internet connection.

Further Information and Manual Repair

Windows 10 error codes are numerous and so are the solutions to fixing these problems. In most cases, Windows users have access to several manual repair solutions depending on the error code present on their device. These manual repair methods are usually easy to implement, with the exception of a few solutions that require technical knowledge and skills. In such cases, you may need to consider using an effective automated tool or you may contact a Windows repair technician to assist you.

In terms of error code 0x80072EE2, however, no technical skills are required. Manual repair solutions for this error code involve checking and troubleshoot network problems if your connection was disrupted. Also, you may need to check your firewall settings and disable it temporarily to verify whether or not your firewall is preventing you from accessing the upgrade. Further details are provided below.

Method One: Verify Internet Connection

If for whatever reason you lost Internet connection while attempting to upgrade your operating system via Windows Update, your upgrade will time out and error code 0x80072EE2 in Windows 10 may occur. For this reason, it is important for you to check your connection once you notice the presence of error code 0x80072EE2 on your device.

There are many ways you can verify your Internet connection but one of the simplest ways is to first open your preferred Internet browser and type the web address of a site you normally visit. Once you are able to access the website, you will know for sure that your connection is not an issue. Simply restart your PC and reattempt the upgrade.

If you are unable to complete the upgrade process, however, this simply means that there is another issue causing error code 0x80072EE2 to occur. Proceed to the next manual repair method. This method may also apply if you were unable to connect to the Internet.

Method Two: Troubleshoot Network Problems

Though you may be able to access a website or open your Internet browser, there may be other issues affecting your network that are causing the error code to occur. To verify for certain whether or not the issue causing error code 0x80072EE2 in Windows 10 is related to your network, troubleshoot your network using the Network Troubleshooter tool found on your PC.

• Step one: Type Network Troubleshooter in the search box near the Start button
• Step two: Select Identify and repair network problems
• Step three: Wait until the troubleshooter has verified and fixed problems related to the network
• Step four: Restart PC

Once the issue has been resolved, it is time to verify if the error code is fixed. Open Windows Update then select the option which enables you to access the latest upgrades to your machine. Wait to see if the error code reoccurs or if you can now access the upgrade to your operating system. If the error code reoccurs, move to the next manual repair method.

Method Three: Disable Firewall Settings

Another issue that may be causing an error code to occur is your firewall. To verify if your firewall is preventing you from accessing the upgrade, disable your firewall. If you are using third-party security software, simply open the security app and check its firewall settings. Select disable or turn off the firewall.

Restart your computer, then open Windows Update to reattempt to upgrade your device. If this proves successful, you will be able to access the upgrade. Error code 0x80072EE2 in Windows 10 will no longer be present.

Method Four: Download an Automated Tool

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

In case you don’t know, there is a built-in tool in Windows 10, known as Reliability Monitor that provides a day-to-day snapshot of the health of your system. It warns users of any looming issues or disasters before your computer breaks down finally. So obviously, Reliability Monitor is useful, however, there are times when it could behave incorrectly. For instance, it might fail to show you any updates even when they are installed. Thus, if you experience any malfunctions with the Reliability Monitor tool in Windows 10, read on as this post will guide you in updating or working in Windows 10. To fix the problem with the Reliability Monitor, there are several fixes you can check out. You can try to enable the data collection for Reliability Monitor or reset it, as well as put your computer in a Clean Boot State. For more information, refer to each one of the options given below.

Option 1 – Try to enable the Data Collection for Reliability Monitor

The Reliability Monitor tool uses data provided by the RAC Agent scheduled task and it will start to display a Stability Index rating and specific event information 24 hours after the system installation. The RACAgent scheduled task, by default, runs after the operating system is installed. And if it is disabled, it must be manually enabled from the Task Scheduler snap-in for MMC or Microsoft Management Console. Thus, you need to enable the Data Collection for Reliability Monitor to fix the problem.

Option 2 – Try to reset the Reliability Monitor

The next thing you can do to fix the issue with the Reliability Monitor might want to reset it to resolve the problem. If the Reliability Monitor is already open, you have to close it and open it again. After the reset is done, it may take up to 24 hours for the Reliability Monitor to display results again. This should fix the problem.

Option 3 – Troubleshot the problem in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing the Black border issue. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Over the years, the Windows 10 updates have smoothened but that does not mean that it no longer encounter some issues. One of these issues is when it gets stuck. As you know, Windows automatically checking for updates regularly or when you click the “Check for updates” button. However, if the Windows 10 update is taking forever and seems to be stuck, then you’ve come to the right place as this post will guide you on what you can do to resolve the problem. This kind of scenario in Windows Updates can be quite confusing especially since there is no response or any indication of what is really happening since you don’t know if the update is still downloading or if it’s already getting installed. To resolve this problem, there are several options you can check out. You can try to exit settings and restart your computer. You could also try to restart the services related to Windows Update or clear both the Software Distribution and Catroot2 folders, as well as run a System File Checker scan. For more details follow each one of the given steps below.

Option 1 – Restart your computer

The most basic thing you can do to fix the problem is to restart your computer. It usually works in fixing common issues like the Windows Update getting stuck at the “Checking for updates” screen. However, if it didn’t work, proceed to the next given options below.

Option 2 – Reset Windows Update components

If the first two options did not work then you might want to reset the Windows Update components manually. Follow the steps below to reset them.

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS, and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below, and don’t forget to hit Enter after you type one command after the other.
  • ren C:WindowsSoftwareDistribution SoftwareDistribution.old
  • ren C:WindowsSystem32catroot2 Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.

Option 3 – Try checking Services Dependencies

Dependencies of a Windows Service in Windows 10 are when windows services depend on other services. Such is the case with the Windows Update service – it also depends on three different services such as the Remote Procedure Call or RPC service, DCOM Server Process Launcher, and the RPC Endpoint Mapper. Meaning to say, if two of these services are not working as expected, then the dependent service will also be affected. This could be the reason why the Windows Update service could not start.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter to open Windows Services.
• From the list of Services, look for the following services:
  • Remote Procedure Call (RPC) Service
  • DCOM Server Process Launcher
  • RPC Endpoint Mapper
• After you find these services, double click on each one of them and check whether the Startup type for all is set to Automatic and the Service status is set to Running or not.
• If the service status is not running, then click the Start button. Afterward, check if you can now run the Windows Update service.

Option 4 – Check the Background Intelligent Service and the Cryptographic Service

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter or click OK to open Services.
• From the list of Services, look for the following services and make sure that their Startup type is as follows:
  • Background Intelligent Transfer Service – Manual
  • Cryptographic Service ­– Automatic
• After that, check if the Service status of the listed services above is set to Running. If they’re not, click on the Start button to start these services and then check if you can now enable the Windows Update service or not.

Option 5 – 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 to good system files that might be the cause why your screen is stuck at “Checking for updates”. 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.

• Restart your computer.

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.