Windows 10 is stuck on Checking for updates

There is one service in the Windows operating system that is responsible for managing all the print jobs as well as handles the interaction with the printer. This service is known as the Print Spooler service. However, if it stops running, then you won’t be able to print anything on your computer. In such a case, you can try to restart the Print Spooler service, and to do that, you have to open the Windows Services Manager and look for the Print Spooler Service. Once you found it, right-click on it and select Restart. If it isn’t running, select Start and if the Service starts working again, then good but if not and you got an error message instead that says, “Windows could not start the Print Spooler service on Local Computer, Error 1068, The dependency service or group failed to start”, then read on as this post will give you a couple of suggestions you can try to resolve the issue. The reason why you could not start the service is most likely because the Print Spooler service is dependent on other services which might not be properly running. If the following services are not running then it’s no wonder why you’re getting the error.

• HTTP Service
• Remote Procedure Control (RPC) Service

You might not see the RPC service which means that the Print Spooler Service does not recognize its dependency on the RPC service. In such a case, you have to manually configure the dependency by following the options given below.

Option 1 – Try configuring the dependency via CMD

The first thing you have to do is to configure the dependency using CMD. Refer to the steps below to do so:

• Open an elevated Command Prompt.
• Then type in “sc config spooler depend= RPCSS” and hit Enter.
• After the command has been executed, restart your computer and then check if it fixed the problem. If not, proceed to the next given option below.

Option 2 – Fix dependency via the Registry Editor

You can also resolve dependency using the Registry Editor. How? Refer to these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to this key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSpooler
• Next, right-click on the “DependOnService” entry located on the right pane and select Modify.
• Now change its value data to “RPCSS” and click OK to save the changes made and then exit the Registry Editor.
• Reboot your computer and see if the issue is resolved.

Option 3 – Try running the Printer Troubleshooter

Another option you can check out is the Printer Troubleshooter. This built-in troubleshooter in Windows 10 can help you fix most print issues. It checks if you have the latest printer drivers and then tries to fix and update them automatically. Aside from that, it also checks if you have connectivity issues or if the Print Spooler and the required Services are running fine. To run it, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “exe /id PrinterDiagnostic” in the field and click OK or hit Enter to open the Printer Troubleshooter.
• Then click the Next button and follow the next on-screen instructions to fix the issue with the printer.

Hal.dll Error - What is it?

Hal.dll error is a type of dynamic link library error that is common in Windows. Hal.dll is the critical file in all Windows installations and the error occurs when this file cannot be correctly loaded. Hal is the abbreviation for ‘Hardware Abstraction Layer’. Communication between Windows and different PC hardware is facilitated with this file. The error causes inconvenience and hampers your ability to use the hardware. The error message is displayed in either one of the following formats:

• "Windows could not start because the following file is missing or corrupt: C:Windowssystem32hal.dll. Please re-install a copy of the above file."
• "Cannot find WindowsSystem32hal.dll"
• "C:WindowsSystem32Hal.dll missing or corrupt: Please re-install a copy of the above file."

Solution

Error Causes

Hal.dll error occurs due to multiple reasons. These include:

• BIOS are not configured properly
• Damaged hard drive
• Hal.dll file is missing, damaged, or corrupt
• Viral Infection

Further Information and Manual Repair

To fix and resolve the Hal.dll error code on your system, you don’t always have to hire a professional technician for the job. Though Hal.dll error is critical but easy to resolve, here are some solutions that you can try to fix it right away even if you don’t have any technical expertise.

1) Restart Your PC

Sometimes this can be a temporary error, so try restarting your PC. If the error is resolved then that’s great. However, if it still persists, then try other solutions.

2) Change the Boot Order

The underlying cause for the Hal.dll error is often not properly configured BIOS; if this is the cause, simply change the boot order of the bootable devices like your hard drive. The BIOS setup utility is used to change boot order settings. This can be done by restarting your PC. Once you restart, press F2 to enter the setup. Now go to SATA operation and change RAID AHCI to RAID ATA. Save changes and then exit. By doing so, you will be able to re-configure the BIOS and resolve the error.

3) Use BOOTMGR

Another way to resolve is to update the volume boot code to use BOOTMGR. To do this, access advanced startup options, open the command prompt and type bootsect command and then press Enter. Run the command and then you’ll get the following message: C: (\?Volume{37a450c8-2331-11e0-9019-806e6f6e6963}) Successfully updated NTFS filesystem bootcode. Bootcode was successfully updated on all targeted volumes. After that close the command prompt. This is most likely to resolve the error.

4) Repair Registry With Restoro.

In case the error is still not fixed, then this means that the problem is bigger than you thought. It may be due to hard drive failure, viral infection, or sometimes because of hal.dll file corruption. In the event of these error causes, it is recommended to download Restoro. Restoro is an advanced, next-generation, and multi-functional PC repair tool embedded with numerous utilities like a registry cleaner, an antivirus, and a system optimizer. The registry cleaner utility:

• Scans for all registry issues
• Wipes out the unnecessary files saved in the hard drive like the junk files, cookies, internet history, and temporary files
• Cleans the disk
• Repairs damaged and corrupt files
• Restores the registry

The antivirus utility scans and removes all malicious software from your PC including viruses, Trojans, malware, adware, and spyware. Simultaneously, it also boosts the speed of your system. It is safe and efficient PC repair software. It has simple navigation and a user-friendly interface. Whether you are using Windows 7, 8 or Vista, it is compatible with all. It can also be used on Windows XP. Click here to download Restoro and resolve the Hal.dll error today!

The Windows Subsystem for Linus, also known as WSL, is a useful and excellent tool for developers. However, it isn’t without flaws as users can still encounter some errors when using it. One of these errors is the error code WslRegisterDistribution, 0x8007019e,0x8000000d. Although it seems like the error is have something to do with the installation of WSL, it could be a false positive since some users who’ve installed WSL still encountered the same problem. Here’s the context of the error:

“Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007019e/0x8000000d Error: 0x8007019e/0x8000000d The parameter is incorrect. Press any key to continue.”

Error code 0x8007019e or 0x8000000d could be due to the absence of supporting Windows 10 features since the error does not even let one use the WSL-based command line. If you are one of the users facing this problem, then you’ve come to the right place as this post will provide you with a couple of suggestions to fix it. There are two options you can check out to fix the problem, but before you do that, you need to make sure that the Windows Subsystem for Linux feature is enabled. The two options include enabling WSL using the “Turn Windows features on or off” option and using the Windows PowerShell.

Option 1 – Try to enable the WSL using the “Turn Windows features on or off” option

• To get started, search for “Turn Windows Features on or off” in the Start Search and click on the appropriate result to open a dialog box.
• After that, you will see a populated list in the dialog box and from there, look for the “Windows Subsystem for Linux” option.
• Once you find it, select OK. This will search and install the system files needed and ask you to restart your computer.
• Restart your computer. The Linux distro should now work without any trouble.

Option 2 – Try to use Windows PowerShell

The next thing you can do to fix the error code 0x8007019e or 0x8000000d is to use Windows PowerShell.

• Tap the Win + X keys and click on the “Windows PowerShell (Admin)” option to open Windows PowerShell as admin.
• After that, execute this command to enable the Windows Subsystem for Linux feature: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
• The command you entered will start to search for the required system files and install them.
• If prompted, type “Y” to restart your computer. This should fix the problem.

Usually when online service is not working or when something goes wrong online it is DNS, well that is what most of the time is the case. And yes, DNS or Domain Name Server seems to be an issue with Facebook being completely down along with Instagram and wassap. The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP. Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted, "By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform." Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things. Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages: "DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures." Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface. Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally." Technicians on site don't know how to do that and senior network administrators aren't on site. It seems that it will all be down for a couple of more hours before the issue is resolved.

When you get the error information, "The Software Can Not Begin Because MSVCR100.Dll Is Missing", what this implies is that the Computer will be lacking the  MS Visual C++ 2010 libraries. The malfunction is rather frequent throughout installations. It doesn't matter the number of times you try to reinstall the program. The malfunction can happen whether you've been utilizing your pc for many years, or it's really a recent one.

Solution

Error Causes

a) Missing MSVCR100.DLL: As the problem message indicates, you get this information mainly because MSVCR100.DLL is completely missing. b) Broken MSVCR100.DLL: When the msvcr100.dll is broken, you will also get the same error, suggesting the software won't start. The thing you need to understand is the fact that MSVCR100.DLL is playing an important role in the application referred to as MS Visual C++ 2010 Redistributable Package. Without the MS Visual C++ 2010 Redistributable Package, any software that you simply make an effort to install won't start. You could possibly complete installing it by pursuing proper installation procedures, and then end up getting the "The Software Can Not Begin Because MSVCR100.Dll Is Missing" error.

Further Information and Manual Repair

If you get the "The Software Can Not Begin Because MSVCR100.Dll Is Missing" error information on an effective setup of any software, you shouldn't worry. You can really repair the issue and commence your recently installed software without any more hassle. Start by checking whether you presently use 64-bit or 32-bit Windows. Visit the start button, in case you use Winxp. Type winver. On the window that appears, click Run, subsequently push enter. Head to Start, in case you use both Win7 or Vista. Subsequently, click on the search box and type “Computer”. Right-click windows and subsequently click on Properties. Under Windows Edition, you'll find whether your Windows is 64-bit or 32-bit. Search for the correct variation of MS Visual C++ 2010 Redistributable Package, as soon as you discover whether your Windows is 64-bit or 32-bit. Down load the x86 variant of MS Visual C++ Redistributable Package if your version is 32-bit and you must obtain the x64 variant of MS Visual C++, for those who own a-64-bit version of Windows Operating System. You must never obtain MS Visual C++ 2010 Redistributable Package from third-party websites. This is because Microsoft doesn't charge a cent for the files. The files are openly and easily available on Microsoft. These files come in many different variants. Consequently, select what's suitable for your own Computer with regards to the version of Windows which you operate.

• Never pick the edition of MS Visual C++ 2010 Redistributable Package that's not compatible or appropriate to your Windows Operating System.

Make use of the release date, when installing MS Visual C++ 2010 Redistributable Package. You might also look out for Service Pack 1 and obtain it for your Windows. Service Pack 1 only ensures that you simply obtain the latest edition. As soon as you end installing the most up-to-date version of MS Visual C++ 2010 Redistributable Package as demonstrated above, reboot your computer and you'll not have to worry about getting the annoying"The Software Can Not Begin Because MSVCR100.Dll Is Missing" error message anymore.

As you know, the NVIDIA Control Panel is the central control panel for all devices that run the graphics drivers manufactured by NVIDIA. This control panel comes bundled with the drive package itself which is why there is no need for users to download it or update it separately. However, recently, some users reported that when they tried to make changes to the configuration in the NVIDIA Control Panel, they were unable to do so and encountered an error message instead saying, “Access denied. Failed to apply selected settings to your system”. If you also got the same error message, then you’ve come to the right place as this post will walk you through fixing this error in the NVIDIA Control Panel. There are several suggestions given in this article to fix the error. You can try to run the file named “nvcplui.exe” as an administrator or restore the most recent version of the folder where the aforementioned file is located. You could also try to restart NVIDIA’s process or restart the NVIDIA Display driver service or update the NVIDIA drivers in your computer. For more details, refer to each one of the options given below.

Option 1 – Try running the nvcplui.exe file as an administrator

• Tap the Win + E keys to open File Explorer and navigate to this path: C:/Program Files/NVIDIA Corporation/Control Panel/Client
• After that, look for the exe file and right-click on it, and then select the Run as administrator option.
• Next, select Yes if a User Account Control or UAC prompt appears.

Option 2 – Try to restore the most recent version of the folder

The next thing you can do to fix the error is to restore the most recent version of the folder where the nvcplui.exe file is located. Keep in mind that this option is tricky so you have to be careful.

• Tap the Win + E keys to open File Explorer.
• Next, navigate to this path: C:/ProgramData/NVIDIA DRS
• From there, right-click on the DRS folder and select Properties.
• After that, go to the Previous Versions, System Protection, or System Restore tab in the Properties window.
• Now restore the most recent version of the contents inside that folder. This will revert the old working configuration of DRS.

Option 3: Restart the process of the NVIDIA Control Panel

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• After opening the Task Manager, look for the process named NVIDIA Control Panel Application.
• Once you found it, expand it and right-click on the NVIDIA Control Panel sub-process, and click on End Task.
• Now try opening the NVIDIA Control Panel from the Start Menu and see if it now works fine or not.

Option 4: Restart the NVIDIA Display Driver Service

• Tap the Win + R keys to open the Run dialog box.
• Then type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• After opening the Services window, you will see a list of services. From there, look for services named “NVIDIA Display Container LS” and double click on it to open its Properties.
• Now make sure that the service is Started. If it isn’t, you need to start it, otherwise, you need to Stop it and Start It again. You also have to make sure that the Startup Type is set to Automatic.
• Do the same for the NVIDIA LocalSystem Container service.
• Restart your computer and check if the problem’s fixed.

Option 5– Try updating the drivers from the official site of NVIDIA

If both the first and second given options didn’t work, you can also try updating the drivers from the official NVIDIA website. And in case you don’t know the type of Nvidia graphics card that your computer is on, follow the steps below:

• Tap the Win + R keys to open the Run dialog box.
• Next type in “dxdiag” in the field and click OK or hit Enter to open the DirectX Diagnostic Tool.
• From there, you can see what type of Nvidia graphics card that your system is on.
• Take note of your graphics card information and then look for the best drivers for your operating system. Once you’ve downloaded and installed the file, restart your PC.

If you got an error message saying, “Windows could not start the Windows Update service on Local Computer, Error 87. The parameter is incorrect” while you were trying to start the Windows update service on your computer, then this post could help you resolve the problem. Along with this error, you might also get any of these error codes such as 0x80240034, 0x80244019, 0x80070643, and so on. Aside from these error codes, you will also notice that the Windows Update service has been stopped. To fix this issue, here are a couple of suggestions that might help but before you go on, you need to create a System Restore point first.

Option 1 – 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 dependant 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 2 – 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 3 – 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 4 – Run the Windows Update Troubleshooter

If resetting the Windows Update components didn’t work, you could also try running the Windows Update Troubleshooter as it could also help in fixing any issues related to Windows Update including this one. 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 5 – Try removing a value from the Windows Registry

If running the Windows Update troubleshooter didn’t help and you receive a message instead saying, “Service Registration is Missing or Corrupt”, you can try to remove a value from the Windows Registry.

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to open the Windows Registry.
• Next, navigate to this path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsSelfHostApplicability
• From this path, look for a value named “ThresholdOptedIn” and if you find it, delete it.
• Exit the Registry Editor and see if you can now enable the Windows Update service.

NDIS or Network Driver Interface Specification is a programming interface for the network interface cards that aids in the proper functioning of a system driver in a computer network. The NDIS helps the computer system in order to communicate with other connected devices and hardware components on a computer network. In relation, the ndis.sys file is a critical system file developed by Microsoft for the Windows operating system. As you know, sys files or system files are important parts of the Windows operating system as well as a repository of system driver settings used by Windows to communicate with the connected hardware and devices. The ndis.sys files are stored mostly in a driver folder at C:/Windows/System32/drivers and as mentioned, these files are essential for the system to function properly. Although the presence of ndis.sys system file is not yet known to affect the normal functioning of the Windows OS, some of the Windows 10 users reported that they encountered ndis.sys blue screen errors on their PCs. Blue Screen of Death errors or Stop errors usually occurs when you open a program or a function. Moreover, it could also occur when the driver gets loaded during the system startup or during system shutdown. It isn’t yet clear what really causes the ndis.sys blue screen error. However, like other Stop errors, it may occur due to corrupted files, misconfigured device drivers, bad drivers, corrupted Windows Registry, missing or damaged system files, and malicious programs. Aside from the aforementioned reasons, the ndis.sys blue screen error might also occur if your hard disk is damaged and if the RAM is corrupted. In such cases, a lot of users usually disable the ndis.sys file. However, it won’t really resolve the issue since the file is required for the normal functioning of the operating system and even when you disable the file, it’s pretty useless as the file will start all over again. In addition, you might want to disable security programs or firewalls and antivirus programs in the meantime to check if these programs are the ones that are causing the error. And if you’ve determined that none of the security programs or firewalls and antivirus programs are to blame, refer to the options below that might help you resolve the DRIVER_IRQL_NOT_LESS_OR_EQUAL or ndis.sys Blue Screen of Death error.

Option 1 – Try to update or reinstall the PC device driver

The Ndis.sys Blue screen error can occur when the device driver in your computer is outdated or corrupted. Thus, you either have to update or reinstall it to fix the issue.

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Option 2 – Rollback your Network drivers

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Next, select the driver entries that are labeled appropriately other than anything in the context of the WAN Miniport.
• Then select each one of them and double-click to open a new mini window.
• After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of your Network adapters.
• Now restart your computer to successfully apply the changes made.

Option 3 – Try running the System File Checker

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the ndis.sys Blue Screen of Death error. 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 4 – Try running the CHKDSK utility

Running the CHKDSK utility might also help you resolve the Netwtw04.sys failed BSOD error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

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

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.

Option 6 – Perform a System Restore

Performing a System Restore on your computer can also help you fix the ndis.sys Blue Screen of Death 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.

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.

Over time Applications change, some for the better some for worse. Some of them even stop receiving updates and are old and vulnerable. Sometimes standards change and some file types are not used anymore. Software evolves along with technology and that is good. Keeping old and useless applications inside your Windows is not so good. From various exploits to simply taking up space, maybe even slowing down OS it is always wise and good to clean your Windows from unwanted old applications. In this article, we will be mentioning some relics of old and providing you with an explanation of why you should remove them from your system if by any chance you still have them on it.

Silverlight

Silverlight was meant to be a competitor for Adobe Flash, it is a WEB framework that enables rich media content inside your WEB browser. The issue is that it is not developed anymore and today's browsers do not support it. The only browser that actually can support it is internet explorer which itself is not supported and how there is practically 0 content on today's modern WEB that will require Silverlight, it is safe and recommended to remove it.

Adobe Flash

Speaking of Adobe Flash, you should remove it as well. Flash has stopped receiving support as of January 2021 and browsers have dropped support for it and even blocked it due to security issues. However, there still might be some local installation of Flash itself inside Windows along with the old Shockwave player that stopped receiving support in 2019. You should remove them both.

JAVA

Now this one is tricky, by itself JAVA does not present any security issues since browsers do not support it anymore and the desktop version is not really slowing down your computer. This one has simply put just another media runtime that is not used and simply takes up space and resources. However if you have some applications that you do use that rely on it (I can really just think of JAVA Minecraft at this point) leave it of course but in any other case, it is just purely not needed.

Quicktime

While we are at media runtime and stuff that just simply is not needed, Quicktime is one of them. Now this Apple Video player and codec is still pretty developed and active in Apple’s iOS environment, Windows version has not been updated since 2016 and it was discovered that it contains some critical vulnerabilities. Uninstall it and if you need a player that could play MOV files, just use a VLC player that can play them without any separately installed codec.

uTorrent

This one, the same as CCleaner was once a good application, as a matter of fact, it was the best torrenting application. Sadly it has fallen from its grace very low, from getting tons of ads in its interface to findings in 2015 that code of torrent client was packed with a crypto miner that used system resources of an installed computer to mine crypto without user’s awareness. You should uninstall this torrent client if you would like to get your PC back and not provide it for cryptocurrency mining for the company that developed it. Use qBittorrent or TIxati, open-source and free ones that have everything needed for any torrenting needs.

Toolbars and Browser extensions

There are a lot of toolbars for browsers and extensions that are malicious in nature or simply not updated providing security issues. It is very advisable to remove this as soon as possible.

WinRAR

WinRAR has gained its large popularity solely for the reason that you could download it from the official site like shareware and use it forever. The license never expired and you could use it indefinitely. Sadly not much has been improved in the application itself and it is slowly falling out in its range of what it can do. There are better open source and free options today like 7zip, PeaZip, ZIPvare, and more that are working the same as WinRAR if not even better.

Windows and manufacturers Bloatware

Yes, applications that come bundled with Windows and with some laptops that include manufacturers made software for different tasks like its own specific media players, calculators, etc. It is known that these applications are not better than their open-source rivals and there are too many of them including some that you will probably never use. It is the same as buying a new phone bundled with tons of applications that you do not need, did not ask for, and do not use. Delete all of them. Considering Windows there are also some Store application like Candy Crush Saga demo and other are safe to remove if not needed. That’s it, our advice for old and not needed applications so you can keep your PC safe and fast.