Logo

How to Resolve Runtime Error 372

What is the Runtime Error 372?

Runtime Error 372 is one of the various types of runtime errors on Windows PC. This error code hampers your ability to access and run Microsoft Visual Basic applications on the system.

Solution

Restoro box imageError Causes

Runtime Error 372 can occur due to multiple reasons:

  • Corrupt application due to viral infection
  • Missing or damaged DLL file
  • Poor PC maintenance
  • Data overload
  • Registry damages

Delay in resolving the runtime error 372  exposes your PC to further problems like the inability to install new programs, Windows startup issues, slow PC performance, system hang-ups, and crashes, etc. Therefore, it is recommended to take measures to resolve the runtime error 372 immediately.

Further Information and Manual Repair

The registry is one of the most critical components of Windows PC. It stores every data and configuration of your computer. Every hardware and software on the system has to connect to the registry to function properly.

However, everyday and frequent PC usage keeps creating wasted, obsolete and invalid entries on your system and saves them in the registry.

And if not cleaned, these files dilate the registry and eventually cause the registry to malfunction. DLL files go missing and often get damaged or corrupt. This leads to runtime error pop-ups like the error code 372.

Furthermore, sometimes the registry also gets damaged due to malware attacks and viral infections. This malicious software damages the registry and exposes your system to serious PC threats like system failures, data loss, and data breaches.

Solutions To Runtime Error 372

To resolve the runtime error 372 on your system, clean and restore your registry. For this, you don’t have to hire a technician and spend hundreds of dollars when you can repair it for free.

All you have to do is download Restoro. This is a powerful one-stop solution for all your PC-related problems. It functions as a registry cleaner and a system optimizer.

Restoro is a user-friendly Windows PC repair tool that can be used by all levels of users. To run and operate this software on your system you don’t have to be a computer programmer or an expert. Its simple navigation and layout make it very easy to use.

It resolves disk fragmentation issues which lead to missing DLL files. It also repairs the damaged and corrupted registry thereby resolving runtime errors like the error code 372.

Restoro is a bug-free, reliable, and efficient tool. It is compatible with all Windows versions.

Click here to download Restoro to repair the runtime error 372 on your PC.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

Fix THREAD_STUCK_IN_DEVICE_DRIVER 0x000000EA
If a program tried and failed to use the Graphics rendering capabilities of a computer, Windows 10 will most likely throw a Blue Screen error that says, “ THREAD_STUCK_IN_DEVICE_DRIVER ”. 0x000000EA is the Stop code for this particular Blue Screen error and could be caused by a bad display driver or bad video card. Whatever the cause is, here are some suggestions you need to check out to resolve this Blue Screen error.

Option 1 – Try to rollback, update, or disable the Graphics card drivers

Since the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error has something to do with Graphics card drivers, you can either roll back, update or disable them depending on your preference in order to resolve the error.
  • 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: You also have the option to 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.

Option 2 – Try removing hardware or drivers that you’ve installed recently

If you have recently installed some hardware or drivers, you might want to disable or remove them since external devices are proven to be one of the factors that trigger Blue Screen errors like THREAD_STUCK_IN_DEVICE_DRIVER. All you have to do is physically disconnect any external devices that are connected to your computer and then check if it fixes the BSOD error or not.

Option 3 – Run System File Checker at boot time

  • Once you get to the Welcome Screen part, click on Next.
  • Afterward, click on the Repair your computer option located on the bottom-left part of the window.
  • Then click on Troubleshoot.
  • Next, select the Advanced Options and then Command Prompt.
  • After opening Command Prompt, type the “sfc /scannow” command and hit Enter to run the System File Checker scan.
  • Wait until the process is completed and type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 4 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like the THREAD_STUCK_IN_DEVICE_DRIVER error. 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.
  • After that, 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.

Option 5 – Try to manually check the Graphics Card hardware

You might also want to check the physical status of your Graphics card and you can do this by disconnecting the Graphics card or any other external device connected to your computer. Once you’ve removed the external device, check it for any damages. If there’s none, connect it back to your computer and check if the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error is fixed or not.

Option 6 – Uninstall any faulty drivers

You can also uninstall any faulty drivers via Device Manager. How? Refer to these steps:
  • Tap the Win + R keys to launch the Run dialog box.
  • Then type “devmgmt.msc” in the field and tap Enter to open the Device Manager.
  • From there, look for any faulty drivers. You can identify them easily as they will be marked with a yellow exclamation point. And then check which entries would not affect the normal functioning of your PC.
  • Now click on the entries of every faulty driver and click on the Uninstall option.
  • Once you’ve uninstalled them, restart your computer to allow your computer to reinstall the faulty drivers you’ve just removed.
Read More
Fix Winload.efi file missing error
The Winload.efi file is an Extensible Firmware Interface or EFI file. EFI files are executable files for the firmware of the computers that are mainly based on UEFI and execute the tasks of loading the files to the bootloader of the computer. They are used for a specific set of tasks such as turning on the computer, installing Windows, restarting the computer or resetting it, and so on. This is why the Winload.efi file is a significant file so if it gets corrupted, lost, or damaged, it would be impossible for the Windows operating system to proceed. Here are some errors you can encounter that are related to the Winload.efi file:
  • efi is missing
  • efi cannot be found
  • efi is missing or contains errors
  • This program can’t start because winload.efi is missing from your computer
  • This application requires the file winload.efi, which was not found on this system.
  • There was a problem starting [path]winload.efi. The specified module could not be found.
In addition, the 0xc0000225 , 0xc00000e and 0xc0000001error codes are also associated with the Winload.efi file. Before you start troubleshooting the problem, you can try to perform System Restore first. This will help undo any changes you’ve made in your computer that might have triggered the Blue Screen error. To perform System Restore, here’s what you have to do:
  • First, press the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” in the field and tap Enter.
  • Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
  • After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.
If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that your create a System Restore point first.

Option 1 – Try rebuilding the Boot Configuration Data (BCD) and repairing MBR

  • Once you get to the Welcome Screen part, click on Next.
  • Afterwards, click on the Repair your computer option located on the bottom-left part of the window.
  • Then click on Troubleshoot.
  • Next, select the Advanced Options and then Command Prompt.
  • Once Command Prompt has been pulled up, the following commands to rebuild BCD files and repair MBR. Don’t forget to hit Enter right after you type each command.
    • bootrec /repairbcd
    • bootrec /osscan
    • bootrec /repairmbr
  • Once the command line is successful in finding out a Windows installation, hit Y to let it boot from the list which will successfully rebuild BCD.
  • Now type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 2 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve errors related to the Winload.efi file. To disable Secure Boot, here’s what you have to do:
  • First, boot your computer into Windows 10.
  • Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
  • After that, go to the BIOS of your computer.
  • Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
  • Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further options including System restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery and UEFI Firmware Settings.
  • Select the UEFI Firmware Settings which will take you to the BIOS.
  • From there, go to Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
  • Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
  • Save the changes made and exit. Afterward, your computer will reboot.

Option 3 – Run System File Checker scan

You might also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:
  • Hit the Win + R keys 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 computer.

Option 4 – Disable the Early Launch Anti-Malware Protection

  • You need to restart your computer in the Start Menu first while holding down the Shift key on your keyboard.
  • After that, it will restart your computer to Startup Settings.
  • Now ensure that the 8th option is labeled as “Disable early launch anti-malware protection.
  • Then tap the F8 key since the aforementioned option above is listed at number 8. This should launch and load Windows on your PC with the Early Anti-malware protection disabled for that session only when you try to carry out the same task and then check if the error related to the Winload.efi file is now fixed.
Read More
Fix The drive is not a valid backup location
USB storage devices are used to store small and even big files, depending on their sizes. Usually, the sizes of the USB vary from 2GB up to 16GB. And as time passes, they have advanced quite a bit and now it’s common to find USB sticks with a capacity of 32GB, 64GB, or even 128GB. And since they now have large capacities, USB storage devices are often used for storing backups of system data as well as creating an image. However, there are times when you might encounter an error message while trying to create a backup or image on your USB device. The error message states:
“The drive is not a valid backup location.”
One of the causes of this problem is that Windows was not able to recognize the USB drives as a valid backup location since USB storage devices weren’t previously large enough to store system images. To fix this error, here are some possible solutions that might help.

Option 1 – Try creating a sub-folder in the USB drive and backup all the images there

The first thing you can try to do is to create a sub-folder on your USB device. This is one good way you can bypass the USB drive limitation. How? Refer to the steps below.
  • First, right-click on the USB storage device and select Format.
  • Next, select NTFS as the File System and check the box next to Quick Format.
  • After that, click on Start to initiate the formatting process.
  • Once the formatting process is completed, open the USB drive and right-click anywhere inside its main drive window, and then select New > Folder.
  • Then name the folder to be created as “Image (or anything you please)”.
  • Afterward, right-click on the folder and select Properties.
  • From there, go to the Sharing tab and click on Share.
  • Now check if the Permission level on the System owner which should be your username is labeled as “Owner”.
  • Then try to back up your files again using your USB drive while keeping the sub-folder as the backup location.

Option 2 – Update the USB Controller Drivers

  • First, click the Start button and type “device manager”.
  • Then click on the “Device Manager” from the search results to open it.
  • From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.
  • Restart your PC and then click the “Search automatically for updated driver software” option.
You also have the option to update the motherboard and the USB driver from the manufacturer’s official website.

Option 3 – Run CHKDSK utility to check the drive for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. To use it, follow the steps below.
  • Tap the Win + S keys to open the Search box.
  • Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
  • After opening an elevated command prompt, copy and paste the following command and hit Enter:
CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]
Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.
  • Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
  • If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
  • After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
  • Wait until the process is completed and then restart your computer.
Read More
Automatically Adjust Active Hours in Windows
In case you didn’t know, the new Windows 10 v1903 has brought tons of new features around Windows 10 Updates. One of these features is the ability to automatically adjust the Active Hours based on your computer activity. This feature is really useful as it tells the operating system when to install the Windows Updates. A lot of users use the Active Hours feature to ensure that the Windows Update won’t force them to restart their PCs to install the update. So if your computer is turned on, it won’t apply the update during the active hours you’ve specified. In addition, the active hours change for many users and they are not that strict. For instance, if you set the active hours between 10 am to 5 pm, Windows Update won’t be forcing you to restart your computer to install the updates at those times. Note that Windows Update allows enabling an option using where it can monitor the active hours in your computer and change it. To configure this setting, here’s what you have to do:
  • Frist, go to Settings > Update & security > Windows Update.
  • Next, take note of your current active hours and click on the “Change active hours” link.
  • Then toggle the option that says, “Automatically adjust active hours for this device based on activity”. This will change the active hours and if you match it with the previous one, it should be different.
As you can see on the image given above, the earlier active hours were between 8:00 to 17:00 and were changed to 11:00 to 19:00. If you have been using this feature for a while you’ll find how useful and handy it is especially when you’re using your computer and don’t want any notifications like the prompts for Windows Updates to bother you while working.
Read More
Fix Defender, The Threat Service has stopped
There are times when you see a message in Windows Defender saying, “The Threat Services has stopped, Restart it now” when you try to use it. This kind of error is usually fixed by simply clicking on the Restart now button. However, if the error still appears even after you restart your computer and you see another message that says, “Unexpected error, Sorry, we ran into a problem”, then continue reading as this post will guide you in resolving this issue in Windows Defender. Before you proceed with the given fixes below, you have to create a System Restore point first. This way, you can always undo any changes you’ve made in case something goes wrong.

Option 1 – Make sure that the Windows Defender Services are started

The Windows Defender Advanced Threat Protection service is the one that protects your computer from advanced threats by monitoring and reporting security events that happen on your computer. This is why you have to make sure that this, as well as other required services in Windows Defender, are set to their default values and are started. To do so, follow these steps:
  • 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
  • After opening the Services Manager, look for the following services and make sure that their Startup type is set to their default values:
    • Windows Defender Advanced Threat Protection Service – Manual
    • Windows Defender Antivirus Network Inspection Service – Manual
    • Windows Defender Antivirus Service – Manual
    • Windows Defender Firewall Service – Automatic
  • You can right-click on each one of the listed services and then select Start to start them.
  • And if some of the services don’t have their default values, just double-click on the Services to change the Startup types and select the correct option from the drop-down menu of the Startup type under the Properties box.
  • Next, set up the Startup type of these services to Automatic and then click on the Start button if the services are not running yet.
  • Now click on the Apply and OK buttons to save the changes made and then see if it fixed the problem or not.

Option 2 – Try modifying some entries in the Windows Registry

If the first option didn’t work in fixing the problem, you can try to alter some entries in the Windows Registry using the Registry Editor.
  • First, tap Win + R keys to open the Run dialog box.
  • Then type “Regedit” in the field and hit Enter to open the Registry Editor.
  • Next, navigate to this registry path: HKLMSoftwarePoliciesMicrosoftWindows Defender
  • From there, look for the “DisabledAntivirus” and “DisableAntiSpyware” DWORDS from the right pane and change each one of their values to “0”. On the other hand, if you don’t see any of these DWORDS, you can create them instead and give each one of them a 0 value.
  • To create a DWORD, simply right-click on any empty space and select New > DWORD. Then name them both as “DisabledAntivirus” and “DisableAntiSpyware”.
  • Afterward, set the value of the newly-created DWORDS to 0.
  • Now exit the Registry Editor and reboot your PC to apply the changes made and then check if it has fixed the error in Windows Defender or not.
Read More
0x800ccc79 Error Code - A Quick Fix

0x800ccc79 Error - What is it?

0x800ccc79 error is an error message that you may come across when sending emails through Outlook Express from Microsoft. This error message is accompanied by a notification that is displayed as ‘email was not delivered’ or ‘the server doesn’t support SSL connection’.

Solution

Download Available to Recover all Lost Outlook data

Restoro box imageError Causes

This error code 0x900ccc79 is triggered due to the following causes:
  • Problems related to email servers
  • Changes in the configuration settings
  • Corrupted Windows Registry

Further Information and Manual Repair

When you receive the error 0x800ccc79 it may hamper your ability to send emails. Therefore it is advisable to fix it to ensure your emails are sent and received without any difficulty.

This Outlook error 0x800ccc79 is quite easy to repair. By following the quick fix 0x800ccc79 error code solutions given below you can resolve this error in just a couple of minutes.

Here’s what you need to do to fix this error right away:

Cause: Configuration issues

Solution: If the error occurs due to Outlook Express being configured to use the SSL protocol while sending and receiving emails via the web, then to resolve it, you need to allow Outlook Express to bypass the Secure Socket Layer settings.

To do so, click on ‘tools’ and then on ‘Accounts’. Now select the email account that you want to modify.

Now select the ‘Properties’ tab and then click on ‘Advanced Settings’.

Here search for the following text message ‘This server requires a secure connection’. Once you locate it, uncheck all the checkboxes given next to this option. After that save the changes and restart Outlook Express to see bring the changes into effect.

Cause: Missing or Corrupt Registry Entries

Solution: If the error 0x800ccc79 occurs due to missing or corrupt registry entries, then the best way to fix this error is to download and install a good registry cleaner on your PC.

The registry cleaner will help you clean your corrupt and damaged Windows registry entries and get rid of this error right away. It is suggested you download the registry cleaner tool from a reliable website to avoid any malware or virus downloads simultaneously.

Once you download the registry cleaner on your system, click on scan. The cleaner will scan your computer completely for registry errors and show you the results in a list form.

After the scanning is complete, click on repair to fix the errors.

So, next time, if you or anyone at your office comes across the Outlook Express error 0x800ccc79, you can try these solutions and fix the error immediately without waiting for the network personnel to come and resolve it.

Read More
0x3D55: Family App information is corrupted
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.
Read More
Software review series: Visual studio code
Visual Studio codeVisual studio code is a code editor available for Windows, Linux, and macOS. It is a completely free tool offering you to code in any language without the need to switch to another editor. Visual Studio Code is part of Microsoft Visual Studio which is a complete integrated development environment (IDE). Take notice that Visual studio itself has more advanced tools for developing and testing, it has 24/7 support, training, and Azure for WEB apps. Visual Studio Code is an editor lacking in some advanced features Visual Studio offers.

Visual Studio code Price and royalty

As mentioned Visual Studio code is completely free licensed under the MIT license agreement giving you the tool free to use and sell your product. How it supports Linux, Windows, and macOS, all you need it to go to its official page https://code.visualstudio.com/, download it and start using it. How this is free project backside is that there is no official support, you will have to rely on various articles and community in order to get needed information or problem solution.

Features

Syntax highlighting has become standard and norm for any editor but besides this function VS code offers us also IntelliSense option which goes a step further with code completion, code hinting, and parameter info. This means that VS code is aware of many things going on inside your code and will offer you as you type a menu with options for autocomplete along with variables referenced, function names, etc. VS code offers extensions inside its extensions marketplace where you can add extensions in order to implement new languages, add debuggers, change the layout, etc. This is one of the great features it allows you to easily switch from one project to another, one language to another not leaving your code editor. Working with version control systems like Git is easy with VS Code. You’ll be able to stage files and make commits, then push and pull changes to your remote code repository of choice, right from the editor.

Conclusion about Visual Studio code

Visual Studio Code is one of if not the most flexible and extensible code editors currently on the market that I have ever tried and used. IT has become my code editor of choice simply for reasons that there is really not much it cannot do and it is constantly updated and taken care of. You can really tune it to look and feels how you want with extensions and you really cannot beat the free price tag. I would highly recommend this editor for daily use especially since its biggest competitors like Atom and sublime text have not seen many updates lately.
Read More
How to Resolve “We couldn’t update system reserved partition” Error in Windows 10 Installation

We couldn’t update system reserved partition” - What is it?

Customers will most likely encounter the “We couldn’t update system reserved partition” error when upgrading to Windows 10 from Windows 7 or Windows 8.1. This error may also come with error code 0xc1900104 or error code 0x800f0922.

Solution

Restoro box imageError Cause

“We couldn’t update system reserved partition” Windows 10 upgrade error is normally caused by too little space on the System Reserved Partition (SRP). The System Reserve Partition is an additional small partition created by Windows, which stores boot files. The SRP can be filled up with security apps and third-party anti-virus. Once this partition has insufficient space, the system will not be able to upgrade to Windows 10.

Further Information and Manual Repair

Caution: The following steps are complex and need to be done by experienced users especially using the command line. Once an error is made in entering commands, there’s a chance that your device can be put in a no-boot situation, or data stored on the device can possibly get lost.

To upgrade to Windows 10, your device needs to have at least 15MB free space on the System Reserved Partition. Follow the procedure below and then try upgrading again.

First, know if the System Reserved Partition is whether in GPT or MBR partition style:

  1. Open the Run window by pressing the Windows key + R. Type msc in the window then press Enter.
  2. Right-click on the Disk where SRP is located then select
  3. Click over the Volumes
  4. On the Partition Style line, you’ll see which partition style your device is using, either Master Boot Record (MBR) or GUID Partition Table (GPT)

Second, determine which method you will need:

Depending on what partition style your device has and whether you’re currently on Windows 7 or Windows 8/8.1, there are various methods you need to do.

Method 1: Windows 7 or 8/8.1 with GPT partition

  1. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.
  2. Type mountvol y: /s at the command prompt then press Enter. This command will add the Y: drive letter where you can access the System Partition.
  3. Type taskkill /im explorer.exe /f then hit Enter. Afterward, restart explorer in Admin mode by typing exe and hitting Enter.

NOTE: While in Admin mode, some apps like OneNote will not run.

  1. Open File Explorer then type Y:EFIMicrosoftBoot in the address bar. Hit Enter.
  2. Choose the language folders you want to permanently delete. Language folders are named with four letters split with a hyphen. For instance, you want to delete the German language: choose de-DE.
  3. Optional: You can also delete unused font files for more space. Type Y:EFIMicrosoftBootFonts in the address bar then press enter.
  4. Once you permanently deleted the unnecessary files, reboot the device to return to explorer.exe to normal mode and remove the Y: drive letter.

Method 2: Windows 7 with MBR partition

Doing this method will make a permanent, but small increase in the free space of the device’s SRP.

  1. Delete language folders

a. Open the Run window by pressing the Windows key + R. Type diskmgmt.msc then hit Enter. b. Select System Reserve partition then right-click on it.

c. Choose Change Drive Letter and Paths then select Add.

d. Type Y for the drive letter then click OK.

e. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

f. Type Y: at the command prompt then press Enter.

g. Once you’ve switched to drive Y, type takeown /d y /r /f . then hit Enter.

NOTE: Ensure that the space and period after “f” is included in order for the command to work properly      

h. Type icacls Y:* /save %systemdrive%NTFSp.txt /c /t then hit Enter to back up the permission to the drive.

NOTE: Ensure that all files are marked as successful and that no files are marked as failed.

i. Type whoami then hit Enter. Record the username that appears. Afterwards, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or the command will not work.

j. In the File Explorer, open the SRP drive and select the Boot folder. Choose the             language folders you want to permanently delete. Language folders are named      with four letters split with a hyphen. For example: de-DE is the German language          while en-US is the U.S. English language.

2. Truncate the NTFS Log:

a. Open the Command Prompt then type chkdsk /L Y: to check the size of the NTFS Log. If the NTFS Log size is less than 5000KB, you need not truncate the file.

b. Type chkdsk /L:5000 /X /F then hit Enter to truncate the NTFS Log.

c. Return to Disk Management window. Select Action menu then select Check if the device’s SRP now has a larger amount of free space. Once there’s enough space, right click the System Reserve Partition then select Change Drive Letter and Paths. Choose Y: then select Remove.

3. If there’s still not enough available space after truncating the NTFS Log, resize the USN journal:

a. Open the command prompt then type fsutil usn queryjournal Y: to display the size in hex value. Convert the hex value to decimal then divide it by 1048576. The result you will get will be in MB. If the journal size is 30MB or more, proceed with truncating the file.

NOTE: To convert the Hex value to Decimal, open the Calculator app in Windows then choose View menu. Select Programmer then choose Hex. Type the Hex value then choose Dec.

b. Type fsutil usn deletejournal /D /N Y: then hit Enter to delete the journal. Type fsutil usn createjournal m=1500 a=1 Y: to recreate the journal having the new log size value.

  1. Restore permissions

a. Type icacls Y: /restore %systemdrive%NTFSp.txt /c /t in the Command Prompt. Check if the files were successfully processed before proceeding. If you see a message saying some files failed while processing, this is normal since some of the files have already been deleted before performing a backup. However, if there are no successful files indicated, the command was not properly executed.

b. Type icacls . /grant system:f /t then hit Enter to adjust the ACL back to System. Now, you can set the owner of the drive by typing icacls Y: /setowner “SYSTEM” /t /c then press Enter.

c. Check if the device’s SRP now has enough free space by going back to Disk Management and refreshing the data. If the SRP already has sufficient space, you can now remove the drive letter. Right-click on the System Reserved Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Confirm deleting the drive letter by clicking OK.

Method 3: Windows 8/8.1 with MBR partition

This method makes a larger, but temporary, increase in the SRP free space.

1. Be sure you have an external drive having at least 250 MB free space and formatted as NFTS.

2. Open Run by pressing the Windows key + R. Type mscthen to choose the Recovery Partition. Right-click on it then choose Change Drive Letter and Paths.

3. Select Add then type Y for the drive letter, click

4. Click on the Start screen then type cmd in the search bar. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

5. Switch to another drive by typing Y: in the command prompt. Once you’re in the drive Y, type takeown /d y /r /f .

NOTE: Ensure that space and period after “f” are included in order for the command to work properly.

  1. Type whoami then hit Enter. Record the username that appears. Afterward, type icacls . /grant <username you got from whoami>:F /t then press Enter.
NOTE: Ensure that there’s no space between the username and “:F” or else the command will not work.
  1. Once the command is completed, type attrib -s -r –h Y:RecoveryWindowsREwinre.wim then hit Enter.
  2. Open File Explorer and check the drive letter of the external drive you’re using (In this case, let’s assume F: is the drive letter of the external drive so when you see F: for the rest of the steps, this means the drive letter of the external drive you’re using).
  3. Type mkdir F:RecoveryWindowsRE in the Command Prompt then hit Enter. Afterward, type xcopy Y:RecoveryWindowsREwinre.wim F:RecoveryWindowsREwinre.wim /h
  4. Type C:WindowsSystem32Reagentc /SetREImage /Path F:RecoveryWindowsRE /Target C:Windows to map the new path
  5. Verify if the copy was successfully done then type del Y:RecoveryWindowsREwinre.wim /F
  6. Return to Disk Management window. Click on the Action menu then hit Check if the device’s SRP now has a larger amount of available space. Once there’s enough space, you can proceed with the upgrade.
  7. Upon completion of the upgrade, move back the wim file to the Recovery Partition. At this point, you can re-map now the location by:
    1. Open the Command Prompt then type xcopy F:RecoveryWindowsREwinre.wim Y:RecoveryWindowsREwinre.wim /h and press Enter.
    2. Type C:WindowsSystem32Reagentc /SetREImage /Path Y:RecoveryWindowsRE /Target C:Windows to re-map to the original path.
  8. Return to the Disk Management window. Right-click on the Recovery Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Remove.

Method: Download a Powerful Automated Tool

Not inclined to go through a long and technical process (as highlighted above)? Download and install a powerful automated tool and get the job done in a jiffy.
Read More
Something went wrong, We couldn’t start
There are instances when you might encounter an error that says, “Something went wrong, We couldn’t start your program” when you open any Office program. This could be due to an issue with the Office file and any Office app you open throws the same error message. This applies to Office 2019/2016, Office 365 Home, Office for Business as well as Business editions. In this post, you will be guided in what you can do to resolve this error. There are several potential fixes for this error, you might only have to restart your computer or you may have to repair Office from Apps and Features or you could also uninstall and install it back again. For more details, follow each one of the provided options below.

Option 1 – Restart your computer

You might be unable to launch any Office app due to some background process that got stuck or there might be some glitch in the system. Thus, the first thing you can do to resolve the error is simply restarting your computer. Once you’ve restarted your computer, open the Office app again or you could also try to sign in back with your Microsoft account that’s connected to Office. If you’re not quite sure which account you were using, you can follow these steps:
  • Open any Office app.
  • Then click on File and look for your name located in the top-right portion.
  • Now click on it. This will display the email or Microsoft account that’s related to Office.

Option 2 – Try repairing Office from Apps and Features

Since Windows 10 offers some repair features that could replace some of the core files with the original files, you can take advantage of such a feature to fix the “Something went wrong, We couldn’t start your program” error when opening any Office app.
  • Open Windows settings and click the Apps and Features option.
  • Next, scroll down until you see the Microsoft Office installation option. Select it and click on Modify.
  • This will open a window and from there, select Quick Repair or Online Repair and click on the Repair button.
Note: When you choose to repair, you might be given two options which depend on how Microsoft Office was installed. For instance, it was installed via Web Installer or Offline Installer (MSI-based). In Web Installer, select Online Repair > Repair when you’re prompted on how you would like to repair Office. While in MSI-based, you have to select Repair under “Change your installation” and then click on Continue. The repair process makes sure that the app data remains untouched.

Option 3 – Try to uninstall and reinstall Office

If neither of the two given options above worked, then you might want to uninstall Office and reinstall it. All you have to do is download the Microsoft Office Uninstall tool from the official site of Microsoft and run it. This will remove any incomplete Office installation as well as unwanted files. It will also get rid of all the Office apps and settings on your computer.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status