Fix NVIDIA Control Panel Access denied

Interrupts are designed so that the resource requests don’t get into a headlock when it comes to the hardware level. To simply put it, it is used to break a loop that never ends. Aside from that, developers also designed levels in order to prioritize interrupts. It is also known as “Interrupt Request Level” or IRQL. And if you suddenly encounter a “Bugcode 0xA –IRQL_NOT_LESS_OR_EQUAL” error, this means that a driver has accessed a memory location illegally while NT is operating at a specific IRQL. The Bugcode 0xA –IRQL_NOT_LESS_OR_EQUAL is a fatal driver coding error and as an end-user, there isn’t much that you can do to resolve it but if you’re a developer, then this means that your code is trying to access an invalid memory location. You could check on different parameters such as memory location that was referenced and code addressed which referenced memory. The technical parameters are:

• a memory location that was referenced
• IRQL at time of reference
• 0 = read, 1 = write
• code addressed which referenced memory

As mentioned earlier, if you are an end-user, there is nothing much that you can do to resolve this problem, but worry not for there are still possible solutions that could help you in fixing it. Refer to the suggestions laid out below to fix Bugcode 0xA –IRQL_NOT_LESS_OR_EQUAL error.

Option 1 – Try running the Hardware and Devices Troubleshooter

The first thing you can do to fix the problem is by running the Hardware Troubleshooter. Although it won’t make much of a difference, there’s still a possibility that it could automatically fix the problem. To use it, refer to these steps:

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

Option 2 – Try to update or rollback your device drivers

If the first option didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

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

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

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

Error Code 47 – What is it?

It is a device driver error that users encounter when they use Windows 2000 operating system and its later versions.

The error occurs when the connected peripheral device, upon removal using the ‘Safe Removal Hardware’ program, hangs up a problem within the process. The error prompt you then see is referred to within the operating system as error code 47.

It usually pops up on your computer screen with the following message:

Windows cannot use this hardware device because it has been prepared for "safe removal", but it has not been removed from the computer. (Code 47)

Solution

Error Causes

There are many factors responsible for the Error Code, the primary ones are listed below:

• An incomplete program installation
• An incomplete program uninstallation
• System recovery from viruses
• Corrupted Windows system registry entries

Further Information and Manual Repair

Error Code 47, like other device driver error codes, is relatively easy to solve. You can fix the error code in the following ways:

Method 1 – Reconnect the device to your computer

Unplugging and plugging the USB cable of the device into the computer is the easiest way to resolve the error.

Doing this will help refresh the system and increase the likelihood of the device driver files loading and function properly.

Method 2 – Restart your PC

Another simple method you can use to solve your PC error code is to simply restart your Windows system.

It may be that the error prompted upon connecting the device you have connected is merely a temporary problem, and upon restart, will resume functioning smoothly.

Method 3 – Manually uninstall then reinstall the device driver

If both of the above-listed methods fail to resolve the problem, you may have to resort to manually uninstalling and then reinstalling the device driver causing the problem.

This would be necessary since the remaining incomplete files due to a partial removal or installation of programs is what contributes to the error code. By uninstall and reinstalling the device driver program, it would lead to the completion of the files.

You can do this by firstly logging in as Administrator and open Device Manager. Select the device that is causing the problem and double click it and make sure that the peripheral is connected properly to the PC.

Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.

Method 4 – Use software to automatically download the driver

Manually uninstalling and reinstalling the driver will usually do the trick; however, it may be time-consuming especially when you would have to resort to your hardware user manual.

Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer.

DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically. It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 47. It also has the added advantage of being able to backup and restores your files should there be the slightest possibility of system file damage. Thus, registry damage can be averted by letting the software roll back the system files to an earlier healthy checkpoint. DriverFIX is the answer to fixing your PC error codes accurately and quickly. Click here to download DriverFIX to fix Error Code 47 quickly and effectively!

What is DISM Error 1726? Every time you encounter some issues in your Windows 10 computer, especially when it comes to corrupted system files, you can always use the SFC scan and if the SFC can isn’t able to resolve the issue, there is also the DISM tool you can use which usually resolve the vast majority of system file corruption sufficiently. However, there are times when even the DISM commands experience issues as well. Such is the case with the 1726 error: “The remote procedure call failed”.

Some users reported that this DISM problem happens right before the process is supposed to end. According to experts, this error in DISM occurs due to any of the following reasons:

1. A third-party program might have interrupted the DISM operation and is the one that triggered the 1726 error: “The remote procedure call failed”.
2. The error could also pop up when there is a pending corruption repair. This usually happens when you tried to run a DISM command previously that was terminated manually or was halted because of some malfunction.
3. Lastly, the error could also occur because the process that’s responsible for the procedure is disabled or was prevented from running.

Whichever the case is, here are some suggestions that might help you in resolving the 1726 error: “The remote procedure call failed”.

Option 1 – Try updating your PC to the latest Windows build available

Since the problem is specific to certain builds in Windows 10, you need to make sure that your computer is updated before you try other troubleshooting steps. Thus, follow the steps below to update your Windows 10 PC.

• Tap the Win + R keys to open the Run dialog box.
• Then type “ms-settings:windowsupdate” in the field and hit Enter to open the Windows Update screen.
• After that, click on Check for Updates and then follow the next on-screen instructions to apply the latest Windows update.
• Once the update has been installed, restart your PC and run the DISM command again and see if the problem is fixed.

Option 2 – Try to change the Startup Type of the Remote Procedure Call service

As stated early on, the error might also be caused by a disabled Remote Procedure Call service or RPC or that it might be prevented from running for some reason. In case you don’t know, RPC is the service control manager for both COM and DCOM servers and it’s responsible for performing object variation requests, exporting resolution as well as distributing collection for the servers. And so if the server is disabled, all programs that are using COM and DCOM including the DISM commands, will not function correctly. Thus, you need to make sure that the RPC service is scheduled to enable itself on every system boot. To do so, here’s what you have to do:

• Tap the Win + R keys to open the Run dialog box.
• Type “services.msc” in the field and hit Enter to open Services.
• From there, scroll down until you see the Remote Procedure Call (RPC) service and then right-click on it and select Properties.
• Then go to the General tab and change the drop-down menu next to Startup type to Automatic.
• After that, click the Apply button and then OK to apply the changes made.
• Restart your PC and run the DISM command once again at the next startup.

Option 3 – Try to modify the RpcSs registry key value

If the option didn’t work, you can also try enabling the RPC service using the Registry Editor. Before you proceed, make sure to create a System Restore point first and then follow the steps below afterward.

• Tap the Win + R keys to open the Run dialog box.
• Type “Regedit” in the field and hit Enter or click OK to open the Registry Editor. And if a User Account Control prompt appears, just click on Yes.
• After that, navigate to this registry key: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services RpcSs
• After selecting the aforementioned registry key, go to the right pane and double-click on the Start value.
• Next, change the Value data of start to 2 and click OK to save the changes made.
• Exit the Registry Editor and restart your PC and check if the 1726 error in DISM has already been resolved or not.

Option 4 – Try to disable the Windows Search service temporarily

Some users also recommended disabling the Windows Search service for the meantime as it could be the one that’s interrupting the DISM process.

• Tap the Win + R keys to open the Run dialog box.
• In the field, type “services.msc” to open the Services window again and hit Enter to open it.
• Next, scroll down over the services list and double-click on the Windows Update service.
• Afterward, go to Windows Search properties and click the General tab and then click the Stop button to stop the service from running temporarily.
• Now try running the DISM commands again and see if the problem’s fixed or not.
• Restart the Windows Search service and then restart your PC as well.

If you encounter an error while trying to burn files to a CD or disk on your Windows 10 computer, stating, “Windows Media Player cannot burn some of the files”, read on as this post will guide you in fixing the error. Here’s the complete error message:

“Windows Media Player cannot burn some of the files. To investigate the problem, click the icon next to the files in the burn list.”

As you know, the Windows Media Player helps you burn songs or audio files to CD or disk but it does not always end up successfully as you could encounter some setbacks such as this particular error. Usually, this kind of issue occurs if an audio file does not comply with some restrictions so the Windows Media Player pops up this error instead. You can encounter this error message if:

• You include a file that’s not an audio file.
• If the total time limit exceeds 80 minutes (even though a CD has 700 MB storage capacity, you can’t burn audio of more than 80 minutes long)

To resolve the error, you have to remove the unsupported files from the burning list, change the burning speed or execute some tweaks in the Privacy settings. For more details, refer to the instructions provided below.

Option 1 – Get rid of the unsupported files from the burning list

You must get rid of the unsupported files from the list of files to burn. This list can be found on the right-hand side of the Windows Media Player. One of the indications that a file is causing problems is when there is a white cross in a red circle next to the file. You can simply click on that icon to remove the file from the burning list. Once you’ve gotten rid of all the unsupported files, try to burn your files to the CD or disk once more.

Option 2 – Try to modify the Privacy settings

In case you don’t know, the Windows Media Player comes with privacy settings that help you in various situations. However, on rare occasions, those settings could also trigger errors and this might be the one that’s causing the “Windows Media Player cannot burn some of the files” to pop up. Thus, you can try disabling these options to resolve the error. How? Refer to these steps:

• Open the Windows Media Player.
• Then go to Tools > Options. If you aren’t able to find the Tools menu, just tap the Ctrl + M keys. On the other hand, you can also tap the Alt key to display the menu options.
• Once you’ve opened the Options window, go to the Privacy tab where you can the “Enhanced Playback and Device Experience” section.
• In this section, you can find the following options. Make sure to disable them all.
  • Display media information from the Internet
  • Update music files by retrieving media info from the Internet
  • Download usage rights automatically when I play or sync a file
  • Automatically check if protected files need to be refreshed
  • Set clock on devices automatically

• After you disable the options listed above, click on the Apply and OK buttons to save the changes made and then try to burn the files again.

Option 3 – Try to change the burning speed

Since the burning speed is set to fastest by default, you can try to change the burning speed to resolve the problem. All you have to do is open the Options window and then go to the Burn tab. From there, select either Medium or Slow burning speed and save the changes made. Now try to burn your files to the CD or disk once again.

Stable Diffusion is a machine learning model developed by Stability AI to generate digital images from natural language descriptions. The model can be used for different tasks like generating image-to-image translations guided by text prompts and upscaling images.

Unlike competing models like DALL-E, Stable Diffusion is open source and does not artificially limit the images it produces. Stable diffusion was trained on a subset of the LAION-Aesthetics V2 data set. It can run on most consumer hardware equipped with a modest GPU and was hailed by PC World as "the next killer app for your PC".

Since Stable Diffusion is run locally and not in the cloud, as mentioned there is no limit to the number of images that you can produce but in order to use it you will have to get down a little dirty with setting your PC environment for it since it is not really an application, it is a command line text based descriptor that will use python to generate your images, so there is no install nor GUI.

In this guide, we will show you how to both install and run Stable Diffusion on your local PC so you can start producing some cool images all by yourself.

Hardware and software requirements

Make no mistake, Stable Diffusion will not run on a potato PC, in order to harvest the power of AI-generated imagery this is what you will need:

• A GPU with at least 4GB of VRAM
• 10GB of hard disk space
• Python and libraries (Miniconda3 installer will install everything you need)
• The Stable Diffusion files
• Git
• Any OS (Windows, Linux, macOS)

Installing components

For this tutorial, we are covering the installation and running of Stable Diffusion on Windows PC. The steps presented here are presented in a way that installation can be performed on any operating system but precise instructions will be for Windows OS.

GIT

The first thing to do is to install GIT. It is a tool that will let you easily maintain and install repos from the internet. to install it go to: https://git-scm.com/ and click on download. Follow the instructions for your version of the operating system. If you are a developer you are familiar with GIT and if you already have it installed you can skip this step.

One thing that is important when installing GIT locally is to select to use it via the command line (the second option that says "Git from the command line and also from 3rd-party software").

Miniconda3

Now when we have GIT installed, next thing is to use Miniconda3 to install python and all required libraries that are needed. Get the installer at: https://docs.conda.io/en/latest/miniconda.html

Miniconda3 is basically an easy installer so you do not have to install tons of stuff manually from different websites and sources, it is nicely packaged in the installer that will take care of everything.

Stable Diffusion

After the previous two steps, we are ready now to actually install Stable Diffusion. Go to https://huggingface.co/CompVis/stable-diffusion#model-access and install the latest library (as of the writing of this article currently it is stable-diffusion-v1-4-original, the last one on the right), the library is almost 5GB in size so be prepared for big download.

After installing stable diffusion's latest library it is time to update it to the newest version. You can download ZIP from GIT HUB https://github.com/CompVis/stable-diffusion

Once downloaded click on the Windows start button and type in Miniconda3 and click on open. Create a folder and name it how you want on a drive of your choice. For this example, we will install it all in disk C under folder AI_art, follow the instructions below but use your own names and destination instead. Do not close Minicoda3 after typing commands!!!

cd c:/
mkdir AI_art
cd AI_art 

Extract GitHub files that you have downloaded into your new folder and get back to Minicoda3 and type the next commands:

cd C:\AI_art\stable-diffusion-main
conda env create -f environment.yaml
conda activate ldm
mkdir models\ldm\stable-diffusion-v1

Let the whole process finish, some files are large and it might take a while. After the whole process is finished and completed, copy the checkpoint file that you have downloaded into: C:\AI_art\stable-diffusion-main\models\ldm\stable-diffusion-v1

After the file is copied rename it to model.ckpt and you are finished.

Running Stable Diffusion

The created environment is needed in order to actually use Stable Diffusion to create images. Each time you want to use it you will have to run it, so go into Miniconda3, and inside it type:

conda activate ldm
cd C:\AI_art\stable-diffusion-main

after we are inside the folder call the script with the parameters:

python scripts/txt2img.py --prompt "TXT DESCRIPTION OF IMAGE THAT YOU WANT TO CREATE" --plms --n_iter 5 --n_samples 1

and that's it, your image is created and it is located in C:\AI_art\stable-diffusion-main\outputs\txt2img-samples\samples

The ntkrnlmp.exe file is a file associated with the Windows operating system’s NT Kernel and other system processes. It is also related to the “CRITICAL PROCESS DIED” error. So if you encounter a Blue Screen of Death error that’s related to this file, then you’ve come to the right place as this post will guide you in fixing the ntkrnlmp.exe Blue Screen error. This kind of Blue Screen error might be caused by the file getting corrupted or infected with some malware. Aside from these causes, the error might also be due to the corruption and malfunction of the graphics card drivers. Before you troubleshoot the problem, you might want to try performing System Restore especially if you tend to create a System Restore point every now and then. Performing System Restore could help you resolve the ntkrnlmp.exe Stop error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

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

If System Restore didn’t help, then proceed to the given options below.

Option 1 – Disable the C-states and EIST in the BIOS

The first thing you can do is try to disable the C-states and EIST in the BIOS. To do that, refer to the steps given below.

• Go to the BIOS and from there look for an option named CPU Configuration which can usually be found under the Advanced menu.
• Next, look for CPU Power Management and under that section, disable both the “Intel EIST” and “Intel C-state” options.
• After you disable them, save the changes you’ve made and exit the BIOS.
• Now restart your computer and check if the ntkrnlmp.exe BSOD error is now fixed.

Option 2 – Try to update, rollback or disable drivers

If the first option didn’t help in fixing the ntkrnlmp.exe Blue Screen error the next thing you can do is to roll back, or update, or disable device drivers in your computer. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 3 – Configure the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. And so if you want to fix the ntkrnlmp.exe Blue Screen error you need to use the Driver Verifier Manager:

• Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
• After that, select the option “Create custom settings”.
• Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
• Next, select the option “Select driver names from a list” option.
• Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
• Then click on the Finish button.
• Open Command Prompt as administrator and execute this command – verifier /querysettings
• The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
• Open the Command Prompt as admin again and run this command – verifier /reset
• The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 4 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like ntkrnlmp.exe. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

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

The network driver error is a not serious Windows issue.  It happens from time to time and luckily it can be solved with a little effort and in a short time period. Today in this article we will explore the most common solutions for driver malfunction for Network adapter inside Windows 10. If you have this particular problem, go from step 1 to the last step since all steps are meant to go from simplest to the most complex. All of that being said let us fix your Network driver issue.

1. Check to see if the cable is plugged in and not malfunctioned

   The first common issue of the network now working can be cable malfunction or bad contact in your network adapter or in HUB/SWITCH. There are various tools to check the quality and working order of cable but you could also make sure that it is not a cable issue by trying connection with the correct working cable. If the network is restored with another cable then change the malfunctioning cable and your issue is resolved if the problem persists move to the next step.

2. Check if Windows troubleshooter will resolve the issue

   Righ-click on the network icon in the taskbar and choose to troubleshoot problems. Windows built-in tools could resolve issues and fix them for you. If by any chance Windows is not able to find or resolve issues move to the next step.

3. Check if the Device Manager is reporting an error and update the driver

   If the hardware is functioning properly then the issue might be in Windows not detecting device or driver malfunction. In any case, the Device Manager will be the one who will report this problem. In order to check to see if the driver is properly working press ⊞ WINDOWS + X to open the hidden start menu. Once it opens, click on Device Manager to open it, If you have a driver device error inside Windows, you should see it immediately when entering the Device Manager, it will have a yellow exclamation mark beside it. Right-click on it and choose update driver.

4. Reinstall driver

   If driver update failed or you already have the latest drivers, reinstalling them could fix the issue since drivers might have corrupted during installation of some update or application. Follow steps from point 3 to get to the driver in Device Manager, then right-click on it but instead of update choose to uninstall. Reboot Windows once the driver is uninstalled and Windows will install a new one automatically. If you do not want to update drivers automatically, do not restart your system, instead install the latest driver for your device, then reboot. Since this is a network error, you will have to get drivers on another computer and transfer them via USB to malfunctioning one.

5. Check Windows update

   Check to see if the latest Windows update is installed, update your Windows if needed

6. Fix driver issue with DRIVERFIX

   If everything else fails, get DRIVERFIX, a premium solution for your PC issues, and fix driver errors.

0x0000007c error inside Windows 11 is a printer error that is manifested when Windows users are trying to connect to a shared network remote printer. Error is displayed by the message:

Windows cannot connect to the printer. Operation failed with error 0x0000007c.

If you are experiencing this type of annoyance, fear now we are providing you with several solutions to this problem.

Update Windows 11

1. Open the Start menu, click on the settings app
2. Select Windows update tab
3. Click on Check for updates
4. Click on Advanced options
5. Inside select Optional updates
6. If there are optional updates click on Download & Install

Run the printer troubleshooter

1. Press ⊞ WINDOWS + I to open settings
2. Click on Troubleshoot navigation on the system tab
3. Select Other trouble-shooters
4. Click on the Run for printer troubleshooter
5. If the error is found click on Apply this fix

Restart the Print Spooler Service

1. Right-click on the Start button
2. Click on RUN
3. Type in services.msc and press OK
4. Right-click on Printer Spooler service and select Restart

Clear the Print Spooler

1. Open services like in the previous step
2. Right-click Print Spooler and select STOP
3. Open File explorer
4. Navigate to: C:\Windows\System32\spool\drivers\x64\3 (64-bit Platform) C:\Windows\System32\spool\drivers\W32X86\3 (32-bit Platform)
5. Delete everything inside folders
6. Go back to services, right-click on Print Spooler and select RESTART

Reinstall Driver for printer

1. Right-click on Start and select device manager
2. Double click on the Print queues category
3. Right-click on the printer and select Uninstall device
4. Click on Uninstall on prompt
5. Right-click on the Print queues category and select Scan for hardware Changes

As you know, Windows has a built-in Automatic Maintenance feature that takes care of important tasks such as security scanning and updating, Windows software updates, Disk Defragmentation, System Diagnostics, Disk Volume Errors, and many more. So if you receive an error message saying, “Windows is unable to run automatic maintenance, The maintenance schedule is unavailable”, then this post will guide you in what you can do to resolve this issue. Here are some suggestions you can try if the Automatic Maintenance in your Windows 10 PC is not able to run.

Option 1 – Enable Automatic Maintenance

It is possible that Automatic Maintenance has been disabled so you can try enabling Automatic Maintenance on your Windows 10 PC. To do so, follow these steps:

• Go to Control Panel.
• From there, select System and Security > Security and Maintenance > Automatic Maintenance.
• After that, set the time you want to run the Automatic Maintenance and then check the checkbox saying, “Allow scheduled maintenance to wake up my computer at the scheduled time”.
• Click OK to save the changes.

On the other hand, you can also enable Automatic Maintenance via the Registry Editor. But before you proceed, you need to create a System Restore Point first.

• Tap the Win + R keys to open the Run dialog box.
• After that, type “Regedit” in the field and hit Enter to open the Registry Editor.
• Navigate to the following path:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleMaintenance

• Next, look for the “MaintenanceDisabled” key and then double click on it to open it and then set its value to “0”.
• Click OK and exit the Registry Editor.
• Restart your computer.

Option 2 – Check the Task Scheduler Services status

Majority of the tasks in Windows 10 run via services. So it is most likely that either the Service has been stopped or is set to the manual which is why Windows is unable to run Automatic Maintenance. Thus, you need to change it to automatic mode.

• Tap the Win + R keys to open Run.
• Type “services.msc” in the field and hit Enter to open Services.
• Next, look for the Task Scheduler service and tap the T key on your keyboard which should take you to the services that start with T.
• Double click on the Task Scheduler service and select the Automatic option under the Startup Type.
• If it is not started yet, click on the Start button.
• Then click Apply and OK to save the changes.

Option 3 – Check the Status in Task Scheduler

You can also try checking the status in the Task Scheduler. Just open the Task Scheduler > Task Scheduler Library > Microsoft > Windows > TaskScheduler. From there, make sure that Idle Maintenance, Maintenance Configurator, and Regular Maintenance are enabled.

Option 4 – Run the System File Checker

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Automatic Maintenance issue. 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. 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 and hit Enter.

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 5 – Run the DISM 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 /Cleanup-Image /RestoreHealth
• The DISM command you entered will repair the corrupted system image. Do not close the window if the process takes a while as it will probably take a few minutes to finish.
• Restart your PC.