Fix Dism.exe error 1392 in Windows 10

So you have just got home from that new computer store with your fancy and all-new mouse, screen, keyboard, etc. You plugged in your new component, Windows detected it, installed drivers for it and it is working like a charm. A few months later down the road and the computer starts little by little to slow down. Plug and play is a great concept, and automatic detection is even greater but how time passes old unused stuff piles in your hard drive and in Windows itself thus slowing down your computer and taxing it more and more as new components and software are added. Old drivers from old components sadly are not removed from Windows itself and over some larger period of time they can pile up and slow down your daily operations on the computer or even cause some problems in it. This guide will teach you how to manually remove old unused device drivers from your Windows so it is fresh and like new again.

Making old devices visible

In order for us to remove old drivers, the first thing we must do is make them visible in our device manager, old drivers are hidden and will not show up, we must make this happen. We do this by pressing WINDOWS + X keys on your keyboard to bring up a hidden menu in Windows. Once the menu appears, click on Command Prompt (admin) Once the command prompt with administrator privileges comes on-screen type in it following string: The device manager will open, go to view > snow hidden devices in order to show unused devices.

Removing old device

Open any category and if there is a device that was once used and still has its drivers in the system it will be shown as faded out. Right-click on the device and click on uninstall device to remove it completely from your system. Please always be careful when removing devices so you do not remove the device which is being used by mistake and always double-check that you are removing something that you used to have on your system. This method will show all hidden devices even ones that are hidden but crucial to the system working properly.

Error Code 32 - What is it?

Code 32, a Device Manager error, pops up when a device driver and other required services related to the driver are disabled.

The error code 32 is usually displayed in the following format:

“A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. Code 32”

When a driver experiences a problem, it is reported to the Device Manager. Though error Code 32 does not cause detrimental damage to your system, it can cause the loss of functionality of the hardware device whose driver is disabled.

Solution

Error Causes

Error 32 may be generated due to several reasons. However, the most common causes include:

• The device driver is outdated
• The device is not configured as the default
• Some other device is providing default functionality
• The device driver is disabled in the registry
• Corruption of registry values in the CD ROM Drive Class registry key

Further Information and Manual Repair

If you come across error code 32 on your PC, then repair it immediately to ensure optimum PC performance. To resolve this error code, try the methods listed below. If you are not a computer programmer, don’t worry!

The listed solutions are easy to perform, require no technical background or expertise and more importantly, these solutions are very effective.

Simply follow the instructions to repair error code 32 on your system in just a few minutes.

Method 1 - Reboot Your PC

Sometimes Device Manager error codes may appear due to temporary issues, which may be resolved simply by rebooting your system. If you are lucky, this might actually work.

By restarting your PC, you might be able to get rid of error code 32. However, if the error still persists, then try other methods given below.

Method 2 - Uninstall and Reinstall the Driver

To resolve error code 32, uninstall and then reinstall the driver. To uninstall the driver, simply follow these steps:

1. Go to the start menu
2. Type Device Manager in the search bar and then press enter
3. Now in the Device Manager, find and then double-click the category of device that you wish to uninstall, for example, click on the Display Adapter to uninstall the graphics card.
4. Once you have located the device and the driver you wish to uninstall, simply right click on it and then click ‘uninstall’
5. Windows will prompt you to confirm device removal changes.
6. Click OK to confirm and proceed.
7. After that, simply restart your system to activate changes
8. To reinstall, go to the control panel and choose Add/Remove Hardware and add a new device.  Follow all prompts to reinstall the device.

Method 3 - Delete Both the Upper Filters and Lower Filters Registry Values

As discussed above, sometimes error code 32 may be triggered due to corruption of registry values.

If this is the underlying cause, then delete both the upper filters and lower filters registry values from the registry. This will take about 5 to 7 minutes. Here’s what you have to do:

1. Go to the start menu
2. Type Regedit in the search box and then press enter
3. Now locate the HKEY_LOCAL_MACHINE folder under  ‘My Computer’
4. Click the |> or (+) icon next to the folder name to expand
5. Here you will see a long list of subkeys
6. Locate the correct class GUID for the problematic device
7. Now click the registry subkey that corresponds to the device class GUID
8. Locate the Upper Filters and Lower Filter values and delete
9. Close the registry editor
10. Restart your PC to activate changes

This will hopefully resolve error code 32 on your system if the error was generated due to registry value corruption. However, if the error continues to appear, then resort to method 4.

Method 4 - Update the Problematic Driver

Locate the problematic drivers and update them with the latest versions. This procedure is effective but time-consuming if performed manually.

It takes several minutes to identify problematic drivers and find the latest and compatible versions for each driver on the manufacturers’ website. And besides, you will have to perform updates continuously to ensure the error doesn’t occur again.

Method 5 - Download DriverFIX to Update Drivers Automatically

To avoid the hassle, download DriverFIX.

This is a cutting-edge and user-friendly software program embedded with intelligent system programming and intuitive technology that identifies problematic drivers and updates them with the latest and compatible driver versions in seconds, automatically and on a regular basis.

By installing it on your PC, you can update all the drivers and repair code 32 in no time.

Click here to download DriverFIX to resolve Device Manager error code 32 today!

Recently, some users reported not being able to boot up their Windows 10 computers. And during the startup phase, at some time, the bootup sequence is halted with a Recovery error along with an error message saying, “Your PC/Device needs to be repaired” with an error code of 0x0000605. This kind of error message indicates that Windows was not able to verify the digital signature for the file as the signing certificate or it could be that it has expired. To resolve this error, you can follow the potential fixes given below and see if you stumble upon a fix that might work out for you.

Option 1 – Change the Date & Time settings in the BIOS

Some users reported that they were able to fix the error by changing the Date & Time settings in the BIOS. Upon checking, they saw that in their BIOS settings, the date was off several years. As a result, the incorrect date and time settings end up ticking the system into believing that the Windows build has expired long before the actual expiration date. You can check if the error pops up due to the same reasons by accessing the BIOS settings. To do so, you have to tap the Boot key that’s associated with your motherboard manufacturer during the initial startup phase. After that, you can search for a particular boot key online or you can also tap keys like F2, F4, F8, F10, F12, and the Delete key. Once you’re able to access the BIOS settings, locate the Date & time or anything similar, and then check if the date is correct or not. If not, you need to change the date to the actual date and then save the changes made and restart your computer and then check if the issue is now fixed or not. Just remember that if the actual date is past the expiration date of the build you have, you need to change it to an older date. If your Windows 10 PC is able to boot back up, you have to update it to a stable Windows build and then go back to the BIOS settings and change the date to the current one else you will definitely encounter Windows update errors in the future as well as security alerts.

Option 2 – Perform a clean install of a stable Windows 10 build

If every system boot fails accompanied by a BSOD error with error code 0x0000605 “A component of the operating system has expired” and you’ve already followed every instruction on option 1, then it’s most likely that your current Windows build has already expired. Remember that almost all the Windows 10 Insider Preview builds (98xx) are created along with an expiration date and when your computer reaches the expiration date, you won’t be able to boot your computer up. Note that the exact expiration date varies based on the build number. And prior to the expiration date, the operating system will start to display some error warnings telling you that the build will expire and urge you to update the most recent build available. And so once the computer reaches its expiration date, it will begin to reboot every three hours until it no longer boots up which is about 2 weeks approximately after the license has expired. Once the expiration date is up and your computer no longer boots up, you need to perform a clean install and then install the latest Windows 10 build to resolve the issue once and for all.

0x80042109 - What is it?

0x80042109 is a Microsoft Outlook error. The 0x80042109 error code occurs mostly while sending emails. The error message is often displayed in the following format:

“Sending reported error (0×80042109): Outlook cannot connect to your outgoing (SMTP) e-mail server.”

Solution

Error Causes

It is not easy to narrow down the cause for the error code 0x80042109. This error can occur due to many reasons. This includes:

• Corrupt emails and PST files
• Incorrect Outlook account settings
• Unavailability of the mail server
• Incomplete Outlook installation
• Spyware or viral infection

Further Information and Manual Repair

To resolve the 0x80042109 error code on your PC, here are some easy and effective DIY solutions you can try:

Method 1 - Check Mail Settings

Check your mail settings to see if your outgoing server SMTP is selected or not. If it is not, then it could be the reason for the issue. To check mail settings and select the option, here’s what you need to do:

1. Click Tools, select Account Settings, and then POP 3 account and click change.
2. Now check your name field and email address.
3. Check the incoming and outgoing mail server fields and make sure that it is correct.
4. Now click on the outgoing server and make sure that the option ‘My Outgoing Server (SMTP) requires Authentication is selected.
5. After that, click Advanced and tick the option that says ‘This server requires an encrypted connection (SSL).
6. Now click OK to confirm settings.

Method 2 - Reinstall Outlook on your PC

The error may also occur due to incorrect Outlook installation. Therefore reinstall it on your PC. To do this first you will have to uninstall the software and then re-install it. Once the software is reinstalled try sending the email again. If it is sent successfully, then this means the error is related to incomplete installation. However, if the error still persists then it is advisable to restore the points by going to the System Restore option and choosing the option ‘Restore My Computer to an Earlier Time’ point. This will revert the changes.

Method 3 - Try Disabling Firewall

If you have firewall program installed on your PC, then try disabling it and then send an email through your Outlook account.

Method 4 - Scan for Viruses

Another way to resolve the error code is to scan for viruses. Viral infection and spyware and also affect your Outlook account and activities. However, installing an antivirus on your PC may slow down its performance as such programs are notorious for doing that. Therefore, it is advisable to download Restoro. Restoro is a next generation and a highly advanced PC Fixer embedded with powerful and multiple utilities including an antivirus and a system optimizer. Its intuitive algorithm enables it to scan your entire PC and remove all kinds of malicious software affecting your system including malware, adware, spyware, viruses and Trojans. The system optimizer utility works simultaneously and ensures your PC performs at its optimum speed. It is safe, bug-free, and efficient. It has a user-friendly interface which makes it simple and very easy to operate. You can download it on all Windows versions. Click here to download Restoro to resolve error 0x80042109 today!

In case you don’t know, a teletype network, also known as Telnet, is a protocol that is meant for internet or LAN communication which is used primarily to control other computers effortlessly. And it is available as a command-line utility in Windows and helps users in opening a command-line interface for the remote computer. However, a lot of users have reported an error that states, “Telnet is not recognized as an internal or external command, operable program, or batch file” when you try to use it. If you are one of these users, then you’ve come to the right place as this post will guide you on how to fix this error in Windows 10. This kind of error means that the Telnet utility is not installed on your computer but Telnet is a default feature in Windows 10 so the protocol mainly is not enabled yet. The Telnet client is disabled by default in Windows 10 and to fix this error, you can try to enable the Telnet Client via Programs and Features or try to install Telnet using an elevated Command Prompt.

Option 1 – Try to enable the Telnet Client via Programs and Features

The first thing you can do is to enable the Telnet client using Programs and Features since it is disabled by default. To do that, follow the steps below.

• Tap the Win + R keys to open the Run dialog box and type “appwiz.cpl” in the field and hit Enter to open the Programs and Features window.
• Next, select the “Turn Windows features on or off” from the options given on the left-hand side.
• After that, look for the Telnet client from the list and check the checkbox next to it and then click on OK to save the changes made.
• Now restart your computer.

Option 2 – Try to install Telnet via an elevated Command Prompt

If enabling the Telnet client using Programs and Features didn’t work, then you can try to do it using Command Prompt instead. To get started, follow the steps given below.

• In the Windows Search bar, type “command prompt” in the field and right-click on Command Prompt from the search results, and select the “Run as administrator” option.
• Next, execute this command to enable the Telnet client: dism /online /Enable-Feature /FeatureName:TelnetClient
• Once the command has been executed, close the Command Prompt and restart your computer.

As you know, Airplane mode is the one that gets devices in such a state where all the wireless connections are turned off. However, recently, there are some reports from users claiming that the Airplane Mode turns on by itself in their Windows 10 computers. This kind of problem could be due to an error with the Network driver, third-party applications, and many other factors. Other users also reported that the Airplane Mode automatically flickers, while some stated that they aren’t able to toggle the option for Airplane mode. There are several options you can try to resolve this problem. You can try to configure the Power Management settings for the driver or run the Network troubleshooter. You could also roll back, reinstall or update the Network driver, as well as troubleshoot the problem in a Clean Boot State. For more details, follow each one of the given options below.

Option 1 – Try configuring the Power Management settings for the driver

The first thing you can do to fix the problem is to try configuring the Power Management settings for the driver. How? Refer to these steps:

• Tap the Win + X keys to open the WinX menu and from there, select the Device Manager to open it.
• Next, expand the Network adapters and select the entry for your Wi-Fi hardware.
• After that, right-click on it and select Properties.
• From there, go to the Power Management tab and uncheck the “Allow the computer to turn off this device to save power” option.
• Once done, restart your computer and see if it has fixed the problem.

Option 2 – Try to run the Network troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 3 – Try to update, rollback or reinstall the Network adapter drivers

The next thing you can do to resolve the problem is to update the Network Adapter drivers by following 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 them.
• Look for the Broadcom Network Adapter and right-click on it, as well as other network adapters that have an exclamation icon, and update them all.
• Restart your PC and see if it helped in fixing the problem.

Note: If updating the network drivers didn’t help in fixing the problem, you can also try to roll back the very same drivers from their previous versions and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly. To reinstall the network adapter drivers, refer to these steps:

• 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.

Option 4 – Try to reset the Network Adapter

You can also try to perform a Network Reset to resolve the problem. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

Option 5 – Try putting your computer in a Clean Boot State

You can also troubleshoot the problem in a Clean Boot state. It could be that there are some third-party applications in your computer that are causing the Airplane Mode to behave in a strange way. So, to isolate this possibility, you need to boot your computer in a Clean Boot State be using these steps:

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• After you’ve set your computer into a Clean Boot State, try to observe if the Airplane mode is now back to normal or not.

Lately, Microsoft has trying to fix Print Nightmare with various methods and patches. The last patch has seemingly fixed Print Nightmare but it has broken the Alt-tab key combination. It has been reported that the latest patch has broken famous key combinations for quickly switching from window to window. It seems that combination is not working or it is switching to desktop, even going to blank screen if switching from the full-screen game.

Fixing the issue

Luckily this issue is easily fixable. The first and easier fix for this issue is surprising to turn off the news and info widget, right-click on it and choose News and interests and then click on turn off. The second solution would be to uninstall the update. Go to Settings, then to Update & Security, and from there view Update History and remove the update.

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

Option 1 – Check for certain Windows Services

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

Option 2 – Try resetting the Winsock drivers

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

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

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

Option 3 – Try running System File Checker or SFC scan

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

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

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

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

• Reboot your PC.

What is Error Code 1309?

Error code 1309 is an error code that occurs when installing either Microsoft Office 2003 or Microsoft Office Project 2003. This error code may hamper your ability to run and use applications associated with Microsoft Office. To ensure installation is successful, it is first advisable to fix this error code. Error 1309 is displayed in any one of the two formats illustrated below. When installing Microsoft Office Project 2003, the error message may pop up as:

Error 1309. Error reading from file:    pathfilename.cab. Verify that the file exists and that you can access it.

When installing Microsoft Office 2003, the error message may appear in the following format: Fatal Error During Installation

Solution

Error Causes

Error code 1309 message may appear during Microsoft Office installation due to several reasons. These include:

• Problems in the Oclncore.opc file. Project 2003 uses this version of the file for program installation.
• Lack of adequate use permission
• The requested file was not found
• Setup registry entries are modified in an unacceptable manner

To avoid inconvenience and access Microsoft Office 2003 or Microsoft Office Project 2003, it is recommended to fix the error immediately.

Further Information and Manual Repair

To resolve this error you don’t need to be a technical whiz. Here are some of the best, easiest, and proven do-it-yourself methods to resolve error 1309 on your computer screen instantly.

Method 1 - Change CacheLevel Settings

If the problem is related to Oclncore.opc file then try changing CacheLevel settings. Follow these steps to work around this method.

1. First, locate the PRJPRO*.XML file in the FILESSETUP folder of the Project 2003 installation source and then open this file in the Notepad.
2. Also, make sure that you do not open the file as read-only and make sure that a checkmark is not displayed next to Word Wrap on the Format menu.
3. The next step is to search the file for the following text string: OCLNCORE.OPC_1033.
4. Now on the line where this string is located, change the CacheLevel=’1’ setting to the following CacheLevel=’3’ save the file back to the original location, and then quit Notepad.

After the changes are activated, try installing the software again on your system. If it installs successfully, then this means error 1309 is resolved. If the error still persists then try other given methods.

Method 2 - Configure security settings to get full permission

When the cause of error 1309 on your PC is related to lack of adequate permission issues, then configure security settings to resolve. To do this, simply locate the folder on your installation drive. Then right-click the folder and click Properties. On the Security tab, click edit and now make sure your user name is added to the list. Grant required security permissions and then click OK to save changes. After this, try installing Microsoft Office 2003 again on your system.

Method 3 - Copy the requested file from another source

If the error 1309 pops up because the requested file was not found, then try this method. Simply copy the file specified in the error to the destination directory. For example, if the error shows data1.cab was not found, then copy this file from another source and paste it into the directory specified in the error description.

Method 4- Remove bad registry entries

Bad registry entries are responsible for registry setup modification. If this is the reason for error code 1309, then download Restoro. This is a user-friendly PC Repair Tool embedded with a powerful registry cleaner. It scans and removes all bad and invalid entries accumulated in the registry. It cleans and repairs the registry resuming it back to its normal function. Click here to download Restoro and repair error 1309 today.

As you know, one of the useful and efficient utilities in Windows 10 is the DISM tool. It can be used with the Command Prompt command line which allows users to carry out various tasks. However, there are instances when the DISM tool could encounter some errors when you try to execute a command. One of these errors is the one that states, “The component store has been corrupted”. This kind of DISM error is due to an error in the image file. When you encounter the DISM Error 14098 when running the DISM tool, you will see the following content in the command line:

“C:>Dism /Online /Cleanup-Image /RestoreHealth /Source:c:testmountwindows /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.10586.0 Image Version: 10.0.10586.0 [==========================100.0% Error: 14098 The component store has been corrupted. The DISM log file can be found at C:WINDOWSLogsDISMdism.log C:>”

There are several fixes you can check out to fix the DISM Error 14098, “The component store has been corrupted”. You can try to run the Restore Health command or reset the Windows Update components, or whitelist the dism.exe in your antivirus program, as well as try to uninstall any recently installed updates. Follow the options provided below for more details.

Option 1 – Run the Restore Health command in a Clean Boot State

• First, you need to put your computer in a Clean Boot State.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• Now open Command Prompt with admin privileges.
• Then type and enter this command to execute it: Dism /Online /Cleanup-Image /RestoreHealth
• Wait until the process is completed and restart your computer.

Note: If the Restore Health command fails, you can use the “/StartComponentCleanup parameter” by executing this command: Dism /Online /Cleanup-Image /StartComponentCleanup

Option 2 – Try to reset the Windows Update components

If by any chance that the second option didn’t work, resetting the Windows Update components could also help you resolve the problem. How? Refer to the following steps:

• 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:/Windows/SoftwareDistribution/SoftwareDistribution.old
  • ren C:/Windows/System32/catroot2/Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.

Option 3 – Whitelist the “dism.exe” in your antivirus program

The DISM error 14098 might also be caused by your antivirus program which could be interfering it from running. To fix this, you have to whitelist dism.exe. How? Refer to these steps:

• Open the Windows Defender Security Center from the system tray area.
• Next, click the “Virus & threat protection” option and then open the “Virus and threat protection settings”.
• After that, scroll down until you find the “Exclusions” and click on the “Add or remove exclusions” option.
• Then click the plus button and select the type of exclusion you want to add and from the drop-down list, select Folder.
• Next, navigate to this path and select the WinSxS folder: C:/Windows/WinSxS
• When a User Account Control or UAC prompt, just click on Yes to proceed.

Option 4 – Try to uninstall recently installed updates

There are times when some Windows Updates affect some mechanism internally when you update your Windows 10 computer. As a result, it causes issues with other components of the operating system which could be the reason why you’re getting the DISM error 14098.

• Go to Settings and select Update and Security > Windows Update.
• From there, click on the “View update history” option and then click on the “Uninstall Updates” option.
• This will open a new window that contains the list of installed Windows Updates.
• Now right click on the Windows Update you wish to uninstall and click Uninstall.