Mapi32.dll Outlook Error - Quick Fix

What is Error 0x8007042c?

0x8007042c is a Windows Firewall error code. This error hampers your ability to turn on Windows Firewall on your PC. Firewall is a network security system. It establishes a barrier between a trusted, secure internal network and another network (the internet) that is assumed unsecure. Error 0x8007042c is displayed in the following format: “0x8007042c” error message when you try to start Windows Firewall

Solution

Error Causes

Error 0x8007042c may pop up on your computer screen because of many reasons. These include:

• Firewall service is disabled
• Malware infection
• Registry corruption

Further Information and Manual Repair

The good news is that this error code is easy to resolve. To repair, you don’t to be technically sound or hire a professional for the job. Try our DIY methods illustrated below to fix the problem by yourself in a few minutes.

Method 1 - Start Firewall Manually

This method allows you to start Windows Firewall service manually and then make sure that it starts automatically in the future. This can be done by following these steps, first, go to the start menu and then type services in the search box. Right-click services and then click RUN as Administrator. Now scroll down until you see Windows Firewall. Then double click on it. After that, click the startup type box and then click Automatic. If ‘Service Status’ is stopped, then click Start. Now click ‘Apply’ and then press OK. Scroll until you see ‘Base Filtering Engine’, double click it. If again the ‘Service Status’ is stopped, click start. Press Apply and then OK to activate changes. Now restart Windows, Firewall will be enabled.

Method 2 - Remove Malware

If the error cause is a malware infection, use the Microsoft Safety Scanner to remove malware immediately from your PC. Download it from Microsoft’s official website, install, accept terms and then run it to perform a quick scan. The Microsoft Safety Scanner will scan and remove all malware infecting your PC. Once this is done, click Start and then type Windows Firewall in the Search box. Click Windows Firewall and the navigation pane of Control Panel; Click Turn Windows Firewall on or off. Click Turn on Windows Firewall for each network location and then press OK to activate changes.

Method 3 - Repair the Registry

Sometimes the underlying cause can be registry corruption. In such a situation, download Restoro. It is a PC Repair Tool deployed with a registry cleaner. It scans and removes all the bad entries and files infecting your PC, cleans and repairs the registry in a few minutes. Click here to download Restoro.

A black screen error inside Windows 11 is a typical screen turning to solid black without any error message. This can be very annoying since it can randomly appear out of nowhere and it will appear while you are using the computer. Worry not, this is not a serious error and we have several solutions for it, so please keep reading and try them as presented in order.

Restart graphic driver

This is the first thing to check if the issue is due to software or driver malfunctioning, there is a shortcut for rebooting graphic driver inside Windows 11. Press WINDOWS + CTRL + SHIFT + B to reboot the graphic driver and see if this fixes the issue. A beep sound should be heard during this process and the screen should turn back to normal.

Check connections

Sometimes the screen can go black due to a faulty connection or cable. If you have it at your hand try a different cable or slightly and gently nudge the existing one to see will screen flicker. If you are on a laptop try gently moving the lid from back to front and pay attention to the screen. If screen flickers or picture returns with this method, cable or connector needs to be replaced.

Clean your computer

The black screen can be because the computer is overheating. If this is the case either fan inside is not working properly or there is a lot of dirt and dust that needs to be removed so airflow can be established again for proper cooling. We have an article on errortools.com on how to properly clean your PC but if you are not technical enough maybe the best solution would be to call someone who is or to take the PC to service for cleaning.

Change The Projection Settings

Press WINDOWS + P to open projection settings, check to see if PC is set to PC screen only. If any other option is selected change it to PC screen only since this can cause random black screen issues.

Uninstall latest updates

If this problem has started to manifest itself during the latest update, go to setting and roll back from the latest update to fix this issue.

Scan system for malware

The black screen can also be caused by various viruses and malware. IF you have anti-virus software, run a full system scan to check it for malware. If you do not have one, download a free one and run a system scan, we recommend Bitdefender.

If you are trying to open a folder or run a program or delete a file but you encounter an error message instead saying, “Error (740), The requested operation requires elevation” on your Windows 10 computer, then this post should help. Make sure that you follow each one of the options given below carefully.

Option 1 – Always run the program as an administrator

There are some apps that require administrator privilege before they can be opened. So if you are got the “Error (740), The requested operation requires elevation” error when you try to open a particular app on your computer, you have to try opening it as administrator instead. On the other hand, if you are already using an administrator account or if you are a member of the administrator group, this option may not work for you so just proceed to the next one but if you’re only using a regular account, then follow these steps:

• First, right-click on the app you are trying to open and select Properties.
• After that, go to the Compatibility tab and check the checkbox labeled “Run this program as an administrator”.
• Next, click the Apply and OK buttons and see if the app opens without any problem.

Option 2 – Try to change the folder permissions

If you encounter Error 740 while opening a folder, then you need to try changing the folder permissions.

• First, right-click on the folder and click Properties.
• Next, go to the Security tab and click the Advanced button.
• After that, check the checkbox labeled, “Replace all child object permission entries with inheritable permission entries from this object” and then click the Apply and OK buttons to save the changes made.

Option 3 – Try disabling UAC

The User Account Control or UAC settings might be the one that’s responsible for Error 740 which is why you have to disable the User Account Control and then verify if it’s the one that triggers the error or not. To do that, simply search for “Change user account control settings” in the Taskbar search box and then drag the blue bar down to the bottom and click the OK button to save the change made.

Option 4 – Select the Elevate without prompting option in the Group Policy Editor

There is an option in the Group Policy Editor which allows you to disable the UAC prompt. Disabling the “Elevate without prompting” option can help in resolving Error 740 and to disable it, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to the following path:

Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options

• From there, go to the Security Options folder where you can find a policy named “User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode”. Double click on it to open its options.
• Now select the Elevate without prompting option from the drop-down menu and click OK.

Socket Error 10060 - What is it?

Socket Error 10060 is basically a connection time-out error. This error occurs when the remote FTP server does not respond to CuteFTP. This time-out error occurs after an FTP session is established but even the server doesn’t respond. The error message is displayed in the following format:

‘Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host failed to respond.’

Solution

Error Causes

Socket Error 10060 may occur due to multiple reasons including:

• Blocked port
• Data connection incorrect settings
• When the web proxy connection setting does not allow enough time to receive a response from the destination website and therefore the connection is timed-out.
• Registry issues
• Viral infection

Further Information and Manual Repair

Here are some of the best and quick DIY methods to resolve Socket Error 10060 on your PC.

Method 1: Troubleshoot the Web Proxy Connection

This method is workable and effective if Socket Error 10060 occurs only when the web proxy service is used. To execute it, here’s what you need to do: install the Winsock Proxy Client on your PC. Disable the web proxy settings under the LAN settings on the Connections tab of the internet options. Once you disable the settings, then try to go to the website that you giving you the error. If the site is accessible, the error is resolved.

Method 2: Increase Web Proxy Time out Settings

If disabling the web proxy settings doesn’t work, then try increasing time-out settings. To do so, you will also have to modify the registry. Remember serious problems may occur if you modify the registry incorrectly.

• Here’s what you need to do, click start, run and then type Regedit in the dialogue box.
• Navigate to the following registry subkey: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesW3ProxyParameters.
• On the right side of the Registry Editor, right-click Request TimeoutSecs and then click Modify.
• Click decimal, they type the number of seconds that you want the proxy service to wait until the session times out.
• To confirm changes, click OK.
• Now restart WWW publishing service by going to start, run and type cmd. Click OK to continue.
• Type net stop iisadmin/y and then press enter. After that type net start iisadmin /y and then press enter. Test the new settings by going to the website that displayed the Socket Error 10060 message.

Method 3: Switch from Passive Mode to Active Port Mode

This method is effective if the error occurs due to incorrect data connection settings. CuteFTP uses passive mode by default so to ensure the error is resolved, you may have to switch from passive mode to active port mode. To make this switch, open the site manager and then click once on the name of the problem website. Now on the Type tab change the data connection type to use the port.

Method 4: Configure Firewall Settings

Sometimes the error may also occur due to Firewall.  To resolve, configure Firewall settings to allow FTP protocol.

Method 5: Download Restoro

Whether the error occurs due to viral infection or registry issues, it is advisable to download Restoro. This is an advanced and multi-functional PC fixer embedded with multiple utilities like antivirus and a registry cleaner. The registry cleaning utility removes junk files, cookies, and invalid entries damaging the registry. It cleans, repairs, and restores the registry while the antivirus removes all types of viruses like spyware and Trojans in seconds thereby resolving socket error code 10060. It is safe, user-friendly, and compatible with all Windows versions. Click here to download Restoro today.

Since Windows 10 introduced the concept of notifications, almost any application installed on your computer sends you one. However, there are times when too many notifications can be quite annoying. Although some of them are important, most of them are not and are only getting in the way of your tasks. So if you don’t like to be flooded with tons of notifications on your Windows 10 computer, say no more as this post will help you out in disabling notifications for any apps installed. And now with the new feature in Windows 10 called Focus Assist, you will be able to manage the level of notifications that you receive. This new feature also allows you to disable all notifications except for the ones from important or priority apps. You will just have to maintain a list of priority applications or you could also disable all the notifications except for the important ones like alarms. In addition, you could also set up some automatic rules such as the Focus Assist timings which means that you can make Focus Assist enabled for a certain period of time during the day or when you are duplicating your display or playing a game and whatnot. So if there is an application that keeps on spamming you with notifications, you can just disable the notifications for that application.

To get started on disabling notifications, refer to the steps given below.

• Step 1: Go to Settings > System.
• Step 2: From there, open Notifications and actions and then scroll down to the “Get notifications from these apps” section.
• Step 3: After that, look for the application that you want to disable notifications for and click on the toggle button that corresponds to disabling notifications for that application. You could also click open to explore additional settings for that particular application.

Note: You can disable notifications or just the notification banners, your choice. Aside from that, you can also control the notification sound as well as its behavior when the computer screen is locked. What’s more, is that you can also adjust the number of notifications displayed in the Action Center or select the priority applications. As stated earlier, Windows 10 gives you control that allows you to customize every nook and cranny of the notification on your Windows 10 computer. Apart from applications, there are also other notifications-related settings that you can control including disabling notifications about tips, tricks, and suggestions as well as summary notifications from Windows Defender that you get every time you use or scan your computer.

If you suddenly encountered the PDC WATCHDOG TIMEOUT BSOD Blue Screen stop error with a bug check value of 0x0000014F, then it’s probably due to a system component that has failed to respond with the allocated period which prevents the system from exiting connected standby. This kind of Blue Screen error could be caused by both hardware and software components. To fix this Stop error, here are some possible fixes you can try that might help but before you proceed, make sure that you create a System Restore point first and boot your computer into Safe Mode with Networking.

Option 1 – Try to rollback, update or disable drivers

The next thing you can do to fix the PDC_WATCHDOG_TIMEOUT Stop error is to roll back, or update, or disable 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.
• After opening the Device Manager, look for the device driver named “IDE ATA/ATAPI controllers” and expand it.
• Then look for the SATA AHCI Controller entry and right-click on it. If you haven’t updated this driver in a while, select the “Update Driver” option. On the other hand, if you’ve just updated this driver, then select the Uninstall Device option.
• Next, follow the screen option to update or uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically if you have chosen to uninstall them.

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 2 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the PDC_WATCHDOG_TIMEOUT Blue Screen error.

Option 3 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the PDC_WATCHDOG_TIMEOUT Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type mdsched.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.

Option 4 – Try to update the BIOS

Updating the BIOS can help you fix the PDC_WATCHDOG_TIMEOUT BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Option 5 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like PDC_WATCHDOG_TIMEOUT. It can be found in 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.

Error 0xA00F4244 or 0x200F4244 is when Windows can not detect the WEB camera in your system and it is usually accompanied by the message: We can’t find or start your camera. There could be several reasons for this error and in this guide, we will cover all of them in order to help you to get back on track and start using your WEB camera which is perhaps now more required than ever in this world we live in.

1. Check privacy settings

   With the latest Microsoft Windows updates come the latest issues and it is not strange that privacy settings can become reset or changed when an update is applied. This is a quick fix to this issue and can be the sole reason why you get this error, go to Windows settings, then to privacy and check to see if the WEB camera is turned OFF, if this is the case turn it back ON and make sure that option Allow apps to access your camera is also set to ON.

2. Check if the camera is enabled

   Sometimes it is by mistake, sometimes by an update but the web camera could be disabled in the device manager of Windows. Right-click on the Windows Start button and click on device manager to open it up, find and expand the cameras category. Right-click on your camera, if it is disabled, you will have the option to enable the camera, if it is enabled and Windows is detecting that it is working fine you will have the option to disable it.

3. Check antivirus settings

   Antivirus and firewall applications are in today's world and life-essential piece of software but they can sometimes create more harm than good, from stopping windows updates to killing important services of applications and preventing internet access being just some examples of their paranoid behavior. Try disabling or turning your protection software OFF and see if your WEB camera will miraculously come back to life. If this is the case, somewhere in the settings of software there is an option that controls this aspect, try to locate it and set it in that way so you are able to use your camera.

4. Reinstall camera driver

   If the previous three solutions failed to produce a satisfactory solution then reinstalling the camera driver might fix the problem. Go to your manufacturer's camera website and download the latest driver for your camera. Go to the device manager and uninstall the driver for the camera, then apply the latest driver and reboot the system.

5. Check connections and cable

   Sometimes an issue is not due to software nature, sometimes it is hardware. Try checking connections and plug the camera in another USB port, twist and turn the cable a little to see is issue cable-related.

6. Check to see if the application supports your camera

   If Windows has detected the camera and is not reporting any issues with it check your application to see if it can detect your camera and that it supports it fully. Sometimes newer applications tend to support only newer camera models. Try to use the camera in other software as well to see if the problem is with the application you are using.

7. Try camera on another computer

   If everything else fails, try the camera on another computer to see if it will work there. If the camera is not working there as well it is probably malfunctioned and broken for good. If it does work there, try to find out what is different in that computer in comparison to yours, maybe it is some service running in the background, certain application configuration, Windows version itself, USB port version, or something else.

What Is 0x000000D1 Error?

Error code 0x000000D1 is a serious error that is displayed when Windows automatically shuts down to protect the system against further damage.

Usually, when this error occurs, the message displayed to the users states something like STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL.

Solution

What Causes 0x000000D1 Error?

Usually, the STOP 0x000000D1 error code is caused by issues like incompatibilities, third-party drivers, driver conflicts, outdated drivers, malicious drivers, and other related problems.

Speaking technically, the message displayed to the user actually means that the kernel-mode driver has tried to gain access to memory at an unreasonably high process IRQL.

If left unfixed, STOP 0x000000D1 error can become quite serious. Increased frequency of occurrence may not only lead to data loss but can cause system corruption as well. That’s why it is crucial to fix it and to resolve the underlying issues causing it as soon as possible.

Further Information and Manual Repair

There are different ways of quickly fixing this error, some of which are briefly listed below as follows.

• The solution advised for advanced users is to start the system and log on to it as the administrator. Then do to Start button. Click on All Programs -> Accessories-> System Tools->  System Restore. Here you will find the option, “Restore my computer to an earlier time”. Click on it and select ‘Next’. A list of restore points will appear in front of you. Select the latest restore point and then click on ‘Next’. The confirmation window will appear again. Click on the Next button again. Restart your computer. Congratulations, you have successfully restored your computer.
• Another way that’s more suitable for novice users goes as follows. Download a repair utility tool. Now install the program. You are most likely to come across a Scan button. Once that happens, choose the Fix/Repair button. Your scan will be completed. The error will be removed. You can then restart your computer again to ensure the error is no longer displayed.

Some other suggestions to keep your computer from encountering these problems in the future are outlined below.

• Update all your drivers. Obsolete or old hardware or software drivers may also trigger this STOP 0x000000D1 error.
• If you have recently installed or modified a driver or hardware and the error has occurred afterward, it is highly likely that the installation or modification has caused it. Revert back to the original settings to steer clear of this driver in the future.

Error 2738 - What is it?

The error code 2738 typically occurs either when you attempt to install a program or uninstall it on Windows Vista and 7. The error message is displayed in the following format:

“Error 2738. Could not access VBScript run time for custom action.”

It is a type of runtime error associated with VB (Visual Basic) Script. It indicates that the VB script engine is not correctly registered on your computer.

Solution

Error Causes

The error 2738 may occur due to multiple reasons. These include:

• Windows VB Script engine is not properly installed or is disabled on your PC
• Registry keys are incorrect
• Corrupt registry entries
• Poor PC maintenance

As this error code may be generated due to registry issues, it is advisable to fix it immediately as it may pose serious threats to your system like system failure, crash and valuable data loss. And complete data retrieval is often the hardest task.

Further Information and Manual Repair

To avoid such threats and to resolve the error 2738 on your PC immediately, here are some solutions that you can try:

Register the VB Script Engine Correctly on Your PC

This can be done by running the command prompt as administrator:-

• Simply go to the start menu, click all programs, and select accessories.
• Right-click on Command Prompt and select ‘run as Administrator’.
• Navigate to the folder that contains the DLL. If you are using Windows 32 bit version, then type cd %windir%system32 into the Command Prompt and then press enter.

Nonetheless, if you are using 64-bit version Windows then type the following command: regsvr32 vbscript.dll and then press enter. This will help you register the VB script engine correctly and resolve the issue.

Download and Run Restoro

If the error still persists, then this means the underlying cause of the error 2738 could be invalid and corrupt registry keys. To resolve either of the causes in seconds, it is advisable to install and run Restoro. Restoro is an advanced, innovative, and multi-functional PC Fixer. This tool is embedded with multiple utilities including a powerful registry cleaner, an antivirus and a system optimizer.  The registry cleaner is a powerful utility that instantly detects all registry issues and resolves them right away. The registry saves all activities performed on the PC. It stores all types of files including invalid registry keys, cookies, internet history, junk files and temporary files. If these unnecessary files are not removed and cleared from the PC, it not only takes a lot of disk space but also damages the registry and dll files. The registry cleaning utility detects all such files and removes them. It wipes out all invalid registry entries and bad keys clean the registry and restores it. In addition to this, this tool can also be used to remove viruses and optimize the system speed. It is a user-friendly and highly functional PC repair tool. It is compatible with all Windows versions Click here to download Restoro on your PC and resolve error 2738 right away!

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.