How to Fix Error 118

If you’ve been using your Windows 10 PC for a long time now, you might have come across a couple of issues – from minimal ones to critical ones like the Blue Screen of Death or BSOD stop errors. One of these BSOD errors you can encounter is the DRIVER_IRQL_NOT_LESS_OR_EQUAL Blue Screen error. This particular BSOD error is caused by iaStorA.sys, iaisp64 sys, Netwtw04.sys, nvlddmkm.sys, ndis.sys, wrUrlFlt.sys, and other driver files on Windows 10. This error indicates that a kernel-mode driver tried to access pageable memory at a process IRQL that was too high. When you encounter this error, just like a typical BSOD error, your computer will abruptly stop and you will see a blue screen with an error message saying:

“Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you. (100% complete) If you’d like to know more, you can search online later for this error: DRIVER_IRQL_NOT_LESS_OR_EQUAL (wrUrlFlt.sys)”

The iaStorA.sys file is a software component that’s related to the Intel Rapid Storage Technology by Intel. It is a software solution supported by Intel Smart Response Technology which allows the PC to communicate with the hardware as well as externally connected devices. The Intel Rapid Storage Technology enables the Peripheral Component Interconnect Express or PCIe storage support, serial ATA RAID or Redundant Array of Independent Disks 0, 1, 5, and 10 support, and the PUIS or power-up in standby is also supported. To resolve this kind of BSOD error, you have to update, roll back or fresh-install the problematic driver. Refer to the options laid out below for detailed instructions.

Option 1 – Try removing the Intel Rapid Storage Technology or IRST drivers

The first thing you can try is to fix the Wi-Fi driver or the Ethernet driver on your computer to resolve the BSOD error. Take note that this option works not only on Windows 10 but also other Windows versions.

• Tap the Win + R keys on your keyboard to open the Run dialog box.
• After that, type “devmgmt.msc” in the field and hit Enter or click OK to open the Device Manager.
• After opening the Device Manager, click on the “IDE ATA/ATAPI Controller” entry and expand it.
• Next, right-click on all the driver entries that are appropriately labeled, and then click on Uninstall device.
• Now restart your PC and check if the problem’s fixed or not. If not, proceed to the next given option below.

Option 2 – Try updating the Intel Rapid Storage Technology or IRST drivers

If you’ve already tried uninstalling the IRST driver but you’re still getting the DRIVER IRQL NOT LESS OR EQUAL Blue Screen error when you use your Windows 10 PC, then this means that the drivers might be corrupted or not compatible with the operating system version that you are using right now. So to fix the problem, you have to update your drivers. To do that, follow the steps below.

• The first thing you need to do is to go to your OEM’s website.
• Once you’re already on the OEM’s website, go to the Drivers section and get the latest version for your device and then try to overwrite it.

Alternatively, you can also update the drivers via the Device Manager:

• Tap the Win + R keys on your keyboard to open the Run dialog box.
• After that, type “devmgmt.msc” in the field and hit Enter or click OK to open the Device Manager.
• After opening the Device Manager, click on the “IDE ATA/ATAPI Controller” entry and expand it.
• Next, right-click on all the driver entries that are appropriately labeled, and then click the Update driver option.
• Now restart your PC and check if the BSOD error is fixed or not.

Option 3 – Try using the System File Checker via Command Prompt

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be causing the DRIVER IRQL NOT LESS OR EQUAL Blue Screen error. 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.

Error Code 7 - What is it?

This is a typical system error that occurs during Windows setup. To be precise, this error may pop on your computer screen during the text mode portion of Windows setup. The setup hangs and stops responding and the error message is displayed in either one of the following formats:

‘The file I386Ntkrnlmp.exe could not be loaded. The error code is 7.’ or ‘The file I386L_intl.nlf could not be loaded. The error code is 7.’

Solution

Error Causes

Error 7 may be triggered due to several reasons but the 2 most common causes for this error code are:

• Incorrect settings of the BIOS
• Faulty RAM modules
• Registry corruption

Further Information and Manual Repair

To resolve this error on your system, here are some easy and effective DIY methods that you can try.

Method 1 - Change Back the BIOS to its Default Settings

If the underlying cause of error code 7 is related to incorrect BIOS settings, then it is recommended to restore default settings to resolve. You can reset your computer’s BIOS (basic input and output system) settings to factory defaults by selecting the restore defaults option within BIOS or by removing CMOS ( Complementary Metal Oxide Semi-Conductor) battery from your unplugged computer for about five minutes. The battery removal method requires opening the computer case, so only attempt it if you are unable to access BIOS. To reset BIOS follow these steps, reboot your PC and then press the key assigned to loading BIOS during your computer boot splash screen. The key assigned to load and access BIOS varies from manufacturer to manufacturer but usually, it's F1, F2, or F12. Once you enter the BIOS, select the ‘Restore Defaults’ option listed in the menu.  I t may be a keyboard shortcut or be under the Advanced settings menu. Confirm settings and then exit BIOS. Hopefully, this will resolve Error 7.

Method 2 - Remove the Faulty RAM

When error code 7 is triggered by faulty RAM modules, then to resolve it simply remove the memory modules that are installed in the computer. If the error code is displayed again after you remove the memory module, remove a different memory module. This procedure requires you to reboot your PC several times to identify the specific memory module that is not working properly.

Method 3 - Repair the Corrupted Registry

Error code 7 is sometimes also linked with registry issues. If the reason for the error occurrence is a damaged or corrupted registry, then simply download Restoro. This is a powerful PC Fixer embedded with a registry cleaner. It is easy to operate and user-friendly. The registry cleaner detects and removes all errors in seconds. It cleans the registry and repairs the damages in no time. Click here to download Restoro.

This post will help you fix the ERR_CONNECTION_RESET error in Google Chrome. This error indicates that the Chrome browser wasn’t able to establish a stable connection or that there really is no connection at all with the website you are trying to open. This error does not occur on all websites though. When you encounter this kind of error message you will see the following message on your Google Chrome browser:

“This website is not available, The connection to example.com was interrupted, Error 101 (net:: ERR_CONNECTION_RESET): The Connection was reset.”

Note: You need to follow the options given below to fix the ERR_CONNECTION_RESET error and make sure to reload the webpage each time you complete following each one of the fixes.

Option 1 – Check the Network Cables and restart the router then reconnect

Of course, the first thing you can try is to check if the network cables connected to your computer or router are properly connected. And if your computer is connected via Wi-Fi, you need to make sure to restart your router once. In addition, you can also forget the Wi-Fi your computer is currently connected to and then try reconnecting again to see if it would work.

Option 2 – Try removing the Proxy

Removing the Proxy might also help you in fixing the ERR_CONNECTION_RESET error in Chrome. Here’s how you can do it:

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 3 – Try to increase the Maximum Transmission Unit (MTU)

You can also try increasing the Maximum Transmission Unit to fix the error. To do so, follow these steps:

• Open Settings and go to Network & Internet > Ethernet.
• From there, take off the Active Wireless / Wired Network Connection.
• Next, open Command Prompt as admin.
• Then type the “netsh interface IPv4 set subinterface “Ethernet 4” mtu=1472 store=persistent” command and hit Enter to execute it.

Option 4 – Flush the DNS and reset TCP/IP

Flushing the DNS and reset TCP/IP could also help in fixing the ERR_CONNECTION_RESET error in Chrome. To do so, refer to these steps:

• Click the Start button and type in “command prompt” in the field.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
  • ipconfig /release
  • ipconfig /all
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip set dns
  • netsh winsock reset

After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.

Option 5 – Disable the AppEx Networks Accelerator feature

The AppEx Networks Accelerator is known to slow down network connections. Some users reported that it slows down the network speed by 70% up to 80% which is why you need to disable it. Here’s how you can do it:

• Go to Settings and select Network & Internet and from there select Ethernet > Change adapter options.
• Next, right-click on the network connection and select Properties.
• Then look for AppEx Networks Accelerator and uncheck its checkbox.
• Now click the OK button to save the changes and then check if the error is now fixed.

Option 6 – Delete the WLAN Profiles

Deleting the WLAN Profiles might be a good idea if you are not able to connect to the internet on your computer and if you’re using Wi-Fi. It could be that the networks that were connected previously have gone rogue which is why it is not connecting properly. And so deleting the WLAN profiles might help you in fixing the ERR_CONNECTION_RESET error.

Option 7 – Reinstall the Network Adapter Drivers

• 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.
• Then right-click on each one of the Network drivers and select “Uninstall device”.
• Restart your PC.

Option 8 – Try to disable the Wi-Fi Miniport

• In the Cortana Search box, type “command prompt” then right-click on the search result and select “Run as administrator”.
• After opening Command Prompt with admin privileges, type the commands listed below and hit Enter right after you key in each one of them.
  • netsh wlan stop hostednetwork
  • netsh wlan set hostednetwork mode=disallow
• Now exit Command Prompt and tap the Win + R keys to open the Run dialog box.
• Type “cpl” in the field and hit Enter to open Network Connections.
• From there, look for Microsoft Virtual Wi-Fi Miniport and right-click on it, and then select Disable.

Option 9 – Start Chrome in Safe Mode

The same with Windows Safe Mode, starting Chrome in Sage mode will open the browser but without all the user settings and extensions. And then try opening the website you were trying to open earlier.

Option 10 – Reset Google Chrome

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up the option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

Error Code 22 - What is it?

Code 22 is a type of Device Manager Error code. Device manager errors are reported by the drivers causing the problem. It indicates that the devices are disabled in the Device Manager. This error code is displayed in the following format:

This device is disabled. (Code 22)

It looks like a very simple matter to enable a device from the Device Manager interface but if the device fails to load then there are likely greater underlying problems with the drivers. Drivers allow hardware devices to communicate with other hardware devices and the operating system. Drivers contain instructions and operating procedures for devices. Without a driver, a hardware device will not function and may not even appear in the Device Manager.

Solution

Error Causes

Common causes of error code 22 are:

• Device is disabled
• Driver is outdated
• The driver is missing or corrupt
• The previous attempt to update the driver failed
• Device is damaged
• The device is not configured as the default device

This means that though the error code 22 typically indicates that the device reporting the error is disabled but other causes can also be associated with the error occurrence.

Further Information and Manual Repair

Here are some of the best and easy do-it-yourself methods to resolve error 22 on your PC. Try these methods to repair the issue.

Method 1

If the error code 22 is triggered due to a disabled device, then all you need to do to resolve the issue is enable the device. To enable the disabled device, follow these steps. Simply go to the start menu and type Device Manager in the search bar. Now click on the Device Manager and then click Actions. After you Click Actions, double click Enable Device. The Enable Device Wizard will pop up. Follow all the prompts from the Enable Device Wizard. This will hopefully resolve the issue.

Method 2

If method 1 doesn’t work then this means the problem is deeper than you think.  The problem can be triggered by the missing, corrupted, or outdated driver for the device reporting the error. In such a situation it is advisable to reinstall the driver for the device. To do this first uninstall the driver for the device reporting error code 22 then reinstall the driver.

• For this simply click the Start menu, go to the control panel and then click Performance and Maintenance, and then System.
• In the new window, you will then see a tab called Hardware and the Device Manager.
• Double click on the device whose driver you need to uninstall.
• Click on the properties window with a tab marked driver. Then click on the driver you want to uninstall.

To activate changes reboot your PC. Now reinstall the latest and updated version of the driver uninstalled using the Plug and Play feature.

Method 3

Sometimes devices can also get damaged due to registry issues. In such an event, install Restoro. It is a PC Fixer deployed with a registry cleaner. The registry cleaner wipes out all the unnecessary and obsolete files damaging the registry and repairs them in a few minutes. Click here to download Restoro.

If you suddenly encounter Activation Error codes such as 0xC004E016, 0xC004F210, 0xC004F034, and 0xC004F00F on your Windows 10 computer, then they all point to the same issue – Invalid Product Key or Version mismatch. When you see any of the aforementioned error codes above, it indicates that you are either entering a wrong product key or you are using an incorrect ISO when installing it on your computer. In such cases, you may see either of the following error messages:

“You are running Windows 10 Pro, but you have a valid digital license for Windows 10 Home.” Or: “The specified product key is invalid or is unsupported by this version.”

If you got the error code 0xC004F00F then it means that you’ve entered a product key for the Enterprise edition of Windows to activate Windows 10 Pro or Windows 10 Home. It could be that you have a key from your work and you accidentally use it on your Home PC. If you got the error codes 0xC004E016, 0xC004F210, then it means that you have entered a product key that is meant for a different edition or version of Windows. On the other hand, if you got the error code 0xC004F034 instead, then it means that you have entered an invalid product key or a product key for a different Windows version. Whichever error codes you have, refer to the possible solutions given below to fix the Invalid Product Key or Version mismatch Activation Error in Windows 10.

Option 1 – Try running the Windows 10 Activation Troubleshooter

The first thing you can do to resolve this Activation error is to run the Windows 10 Activation Troubleshooter. To do so, follow these steps:

• Go to Settings and then select Activation.
• After that, click on the Windows Activation and then troubleshoot. This will help you address most of the commonly found activation issues in Windows devices.

Option 2 – Try purchasing a new license

There is an exception offered by Microsoft – if you are connected to a Microsoft account prior to the hardware change, then you can most certainly use the same license key to reactivate Windows 10 again. Microsoft calls this an “Exception path” which should be fixed easily by the Windows Activation Troubleshooter as pointed out earlier. However, if the Windows Activation Troubleshooter isn’t able to resolve the error you can try purchasing a new license. In such rate case, even if you do have a Microsoft account available on your Windows 10 computer, and if Windows was never activated, this solution will not work. And if you haven’t connected your Microsoft account with your Windows 10 computer prior to the major hardware change, then your only option left is to purchase a new license. For you to do that here are some steps you can follow.

• To purchase a new Windows license, the first thing you have to do is click on the Start button > Settings > Update & Security.
• From there, go to Activation and select the “Go to Microsoft Store” option.
• After receiving your new license, you need to go back to Update & Security then go to Activation and select the “Change product key” option.
• Now update your Windows 10 computer using the new key and it should automatically activate your computer.
• Next, you have to create a Microsoft account or connect to your existing local account to your online account.
• Once the system links the key and the account, you need not buy a new license in case something like this happens again.

Note: If you are an IT administrator, you need to keep in mind that there is a limit to the number of times you can reactivate Windows on your computer. Moreover, if you don’t see any option to reactivate the license, and it is a work computer, you need to contact your organization’s tech support.

Option 3 – Try activating Windows 10 via mobile phone

Activating Windows 10 can also be done using your phone. Just note that you have to call Microsoft to do so.

• In the Start Search box, type in “Slui 4” and tap Enter.
• Next, select your country and click on Next.
• Keep the window open and call the toll-free number of the country you’re from.
• Afterward, a confirmation ID should be given by the automated system which you must take a note of.
• Finally, in the box on the window, type in the confirmation ID and click on the Activate button. That should do it.

Being in the Microsoft Windows insider program will let you get a hands-on new Windows 11, but some people just want Windows 11 without being in the insider program. Well, people beware! It was detected that some groups have been releasing fake Windows 11 installers with malware into them. There’s one malicious file called 86307_windows 11 builds 21996.1 x64 + activator.exe. Based on the filename, one might guess that it includes Windows 11 build 21996.1, and on top of that, there’s something in it that will automatically activate Windows for you. It comes in at 1.75GB, so for some people, that might seem reasonable. It starts out looking like a normal installer, and then there’s a second installer that calls itself a download manager. If you accept the nonsense agreement that’s included, you get a bunch of malware. This is just one example of malicious installers running amok internet, but there are more of them with different software placed inside. Malware can be anything from adware to a Trojan virus. The adware usually isn’t super dangerous. It’s just malware that’s meant to inject your PC with advertisements. Viruses can be more of an issue, and they can be harder to get rid of if your machine is infected. Windows Defender does a good job of getting rid of this stuff. The only problem is that if you’re downloading Windows 11 from shady sources, you’re probably already set to click through the dozen or so warnings that pop up telling you not to install it. The solution will be to get Windows from a trusted source of roll inside the insider program and get it from Microsoft directly.

There are times when after you upgrade your Windows operating system, the System Logs under the Event Viewer will display an error message saying, “Event ID 10010 error – The server did not register with DCOM within the required timeout”. What is DCOM? DCOM stands for “Distributed Component Object Model”. It is a proprietary Microsoft technology that allows the Component Object Model or COM software to communicate across a network. You can consider it as an extension of COM which is equipped with the capability of solving a couple of inherent problems related to the COM model to the better use over a network. COM is a tool that’s used for advanced configuration and troubleshooting in Windows 10. Developers usually use it to configure routine components and application behavior like participation in transactions and object pooling and so on. The Component Services needs the DCOM wire protocol in order to communicate with the Component Object Model components on other computers. By default, in a Windows-based system, the network computers are configured initially to enable DCOM. There are also some components in Windows that might require registering themselves with DCOM. However, if they fail to do so, you will encounter the “The server did not register with DCOM within the required timeout” error. To fix this, here are some suggestions you can check out.

Option 1 – Try to use the Component Services

• Tap the Win + R keys to open the Run dialog box.
• Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
• Next, double click on the Computers folder located in the right pane and right-click on My Computer, and select the Properties option.
• After that, switch to the COM Security tab under My Computer Properties and then go to the Access Permissions section.
• From there, click the Edit Default button and in the new window that appears, apply the correct permission to objects under the Group or user names section.
• Once you’re done, click OK and exit. This should fix the error.

Option 2 – Make sure that Function Discovery Resource Publication Properties Services is running

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
• Next, scroll down and look for the “Function Discovery Resource Publication” entry and double click on it.
• Then switch to the General tab and from there, make sure that the Startup Type is set to “Manual (Triggered).
• You also have to make sure that the service is running so if it’s not, just click on the Start button to start the service.
• Now click on Apply to save the changes made.

Option 3 – Try resetting the default DCOM permissions

• Tap the Win + R keys to open the Run dialog box.
• Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
• After that, expand Component Services > Computers and right-click on My Computer, and then select Properties.
• Next, go to the Default Properties tab, and in the Default Distributed COM Communication Properties section, make sure that:
  • Default Authentication Level is set to Connect
  • Default Impersonation Level is set to Identify.

According to some reports, using RDP or Remote Desktop Protocol on recent versions of Windows 10 results in a black screen. One encounters this issue is when using the Remote Desktop Connection feature on Windows 10. The real causes of this black screen are either the display drivers or some misconfiguration with the Remote Desktop Connection utility. In most cases, the Remote Desktop in Windows 10 will display a black screen and then disconnects afterward. To fix this kind of issue on your Remote Desktop, there are two suggestions you need to check out. First, you can try to disable the persistent bitmap caching, and then you can also try to update your display driver. Follow the given options below for more troubleshooting instructions.

Option 1 – Try to disable Persistent Bitmap caching

The first thing you can do to resolve the black screen issue with the remote desktop is to disable the persistent bitmap caching. All you have to do is follow these steps:

• First, open the Remote Desktop Connection client.
• Next, click on the Show Options button to configure the Remote Desktop Connection.
• After that, go to the Experience tab and uncheck the Persistent bitmap caching option.
• Once done, you should now be able to connect to the remote computer without the black screen.

Option 2 – Try to update or rollback the Graphics driver

You can try to update your Graphics card driver using the Device Manager in your computer to resolve the blank dialog boxes problem or you can also go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it. To update your Graphics driver via Device Manager, refer to these steps:

• First, boot your computer into Safe Mode.
• After that, 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. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: If updating the Graphics driver didn’t fix the problem, you can also try to roll back to its previous version and see if that helps or you could also try to roll back, update or reinstall the Network Adapter drivers.

Option 3 – Try performing a System Restore

You might also want to perform a System Restore that might help you in fixing the 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.

There are not many applications for creating mind maps, even fewer that are completely free, so it is with great pleasure to present you with Freeplane. Freeplane is mind mapping, Knowledge Management, and Project Management software completely free and open source. You can it here: https://sourceforge.net/projects/freeplane/files/latest/download

And from developers git page and I quote:

Freeplane is a free and open-source software application that supports thinking, sharing information, and getting things done at work, in school, and at home. The core of the software is tools for mind mapping (also known as concept mapping or information mapping) and using mapped information. Freeplane is written in Java using OSGi and Java Swing. It runs on any operating system that has a current version of Java installed. It can be run locally or portably from removable storage like a USB drive. We use Github only as of the main code repository, all other project parts are hosted at the source forge. So all bugs and feature requests are managed in a separate issue tracker. There is a drop-down box for selecting different types of issues. Other sources of inspiration are our new forum and old forum. Some users write their ideas there. Every contributor and every team member freely decides what task he is going to work on, but for making the best decision we can communicate our self-set goals in the above forum. It is supposed to enable early discussions and community feedback and also to motivate you and other people.

How to start hacking and contributing

People new to the project can start with implementing a new small feature or doing some refactoring or documentation and not with the bug fixing. Not all bug reports seem to be equally important, and if there are important bugs they usually get fixed by people who broke the functionality. I think you should first get there :). For internal developer discussions, there is a private mailing list. It is held private to avoid spam mails. If you want to be subscribed let us know what mail address you are going to use with it. This list is the preferred way to ask all code-related questions because they usually get answered soon and by the most competent team member. Some documentation for new developers is available in Freeplane wiki https://www.freeplane.org/wiki/index.php/How_to_build_Freeplane and also here and here. It is written for new guys and should also be maintained by the new guys to stay up to date. Looking forward to any questions and contributions, Freeplane development team

What is 0x3D55? As you know, Windows 10 is loaded with various Universal Windows Platform or UWP apps such as the Microsoft News, Weather, Calculator, Windows Mail, and many other applications that are based on the modern UWP platform of Microsoft that was introduced in Windows 10. Each one of these apps has a shared piece of code in the kernel for them to be able to get executed across any device that runs the Windows 10 OS which includes laptops, PCs, 2-in-1 devices, mobile phones, mixed reality headsets, and many more. However, there are times when the runtime information for these apps ends up getting corrupted which causes them not to function as expected and throws errors like the error 0x3D55. This kind of error can be pinned down when the UWP app malfunctions and you can also find an error message in the Event Log that reads, “0x3D55: Package family <App name with ID> runtime information is corrupted”. So if you encounter this error, read on for this post will walk you through fixing it. There are three suggestions you need to check out to fix this error – first, you can try to reset the Microsoft Store cache, second, you can try to re-register or reinstall the problematic app and lastly, run the Windows Store App troubleshooter.

Option 1 – Try to reset the Microsoft Store cache

Just like browsers, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 2 – Run the Microsoft Store Apps troubleshooter

The Microsoft Store Apps Troubleshooter will help you in fixing the error 0x3D55. This is a great built-in tool from Microsoft that helps users fix any app installation issues. So this is worth a try to solve the problem. This built-in tool also helps you fix the Windows 10 Store if it isn’t working. To use the Windows Store Troubleshooter, follow the steps below.

1. Tap Win + I keys again to open the Windows Settings panel.
2. Go to Update & Security and then go to Troubleshoot.
3. On your right-hand side, scroll down to find the Windows Store Apps and then click on the Run the troubleshooter option and see if it fixes the problem.

Option 3 – Try to re-register the UWP app via PowerShell

• First, type “command prompt” in the Start Search and right-click on Command Prompt and then select the “Run as administrator” option.
• Next, navigate to this location in the command line utility: C:/Users/<Insert Username>/AppData/Local/Packages
• After that, execute the “DIR” command to view the list of all the directories in the given location.
• Once the list appears, look for the ID of the problematic app and take note of it.
• Now tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

PowerShell -ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage Microsoft.<YOUR APP ID HERE>).InstallLocation + 'AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"

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