Was unable to initialize the windows registry

30.05.202131.05.2021 admin 0 Comments

How to Fix ‘Windows was unable to load the registry’ Error

Several users have been reaching us with questions after they discovered a persistent error inside the Event Viewer that reads “Windows was unable to load the registry. This problem is often caused by insufficient memory or insufficient security rights”. Most affected users didn’t report any associated symptoms with this issue (other than this recurring error message). The issue isn’t exclusive to a certain Windows version as it’s also encountered on Windows 10, Windows 8.1 and Windows 7.

Windows was unable to load the registry files

What is causing the “Windows was unable to load the registry”?

We investigated this particular issue by looking into various user reports and the repair strategies that are most commonly being used to fix this particular behavior. As it turns out, there are several different culprits that might be responsible for this error message. We went ahead and created a list with the most likely elements that might end up causing this issue:

If you’re currently looking for ways to resolve this error message, this article will provide you with several different troubleshooting steps. Down below, you’ll be able to find a collection of methods that other users in a similar situation have successfully used to resolve the “Windows was unable to load the registry” error.

In order to remain as efficient as possible, we advise you to follow the potential fixes below in the order that they are presented since we ordered them by efficiency and severity. Eventually, you should stumble upon a fix that will resolve the issue regardless of the culprit that’s causing it.

Method 1: Removing malware infections (if applicable)

If you suspect that the “Windows was unable to load the registry” error might be caused by some type of malware, adware or spyware that ended up corrupting some system files, it’s important to ensure that the virus infection is completely removed before you try to repair the corrupted files.

The quickest and most effective way to do this (in our experience) is to deploy a Deep Malwarebytes scan and let it inspect your whole system and all of your peripherals (not just the Windows drive).

If you’re not exactly sure on how to do this, refer to this article (here) for step-by-step instructions on running a Deep Malwarebytes scan.

Once you complete this process and you ensure that all virus traces have been removed, move down to the next method below.

Method 2: Repairing System File Corruption

Since most culprits that might end up causing the “Windows was unable to load the registry” error inevitably lead up to System File corruption, you need to take the steps necessary to resolve any type of corruption that might affect your operating system.

In this case, the easiest and most effective ways to repair any degree of System File corruption is with utilities like System File Checker (SFC) and Deployment Image Servicing and Management (DISM).

Both of these built-in tools have virtually the same capabilities, but they do things in various different ways. The first one (SFC), uses a locally stored cache to replace corrupted system files with fresh copies while DISM relies on Windows Update to download fresh copies in order to replace corrupted items that it manages to detect.

Since DISM was designed as sort of a backup plan in case SFC fails to remove the corruption, we advise you to run both utilities in order in order to fix the corruption and resolve the “Windows was unable to load the registry” error.

Here’s a quick guide on running SFC and DISM scans from an elevated Command Prompt:

If you’re still seeing new events with the “Windows was unable to load the registry”, move down to the next method below.

Method 3: Deleting the UsrClass.dat file

Some users that have been encountering this issue on Windows 10 with symptoms like malfunctioning search function or Start menu not expanding have to manage to resolve the issue by deleting the UsrClass.dat file from the AppData folder.

Under certain circumstances, this procedure deletes some corrupted registry key, which forces Windows 10 to create a new healthy copy that will not have the same issue.

Here’s a quick guide on deleting the UsrClass.dat file:

If you’re still seeing new Event Viewer errors with the “Windows was unable to load the registry” message, move down to the next method below.

Method 4: Creating a new user profile

Since in most cases, the issue is caused by a corrupted user profile, in most cases you’ll be able to resolve the issue by creating a new profile for your Windows computer. Upon completing this procedure, any corrupted dependencies associated with the current user profile will be replaced with healthy copies.

Several affected users have reported that they managed to resolve the issue by creating a new user profile. The “Windows was unable to load the registry” error no longer occurred once they made the switch to the new account.

Here’s a quick guide on creating a new user account on Windows 10:

If you’re still experiencing the same symptoms, move down to the next methods below.

Method 5: Using a previous restore point

If you noticed that the issue only started to occur recently, you might be able to work around the issue by restoring your computer to a healthy point where the “Windows was unable to load the registry” error was not occurring.

All recent Windows versions will allow you to return your system to a healthy state by using restore points that were previously saved. If you’re lucky enough to have a restore point saved prior to when the issue started occurring, you should have no issues resolving the error.

But keep in mind that this procedure will also revert any other modifications that have been made since the restore point has been saved. If you want to go ahead with this potential fix, here’s a quick guide on doing a system restore:

If you still see new events with the “Windows was unable to load the registry” error, move down to the next method below.

Method 6: Performing a repair install

If none of the methods above have allowed you to resolve the issue, this procedure should allow you to resolve any scenario that is occurring due to system file corruption. The preferred approach would be to use a repair install to reset all Windows components including all related booting-related processes. The beauty of this method is that this procedure will not touch anything else other than Windows components.

As opposed from a clean install, you’ll be able to keep all your personal data including applications, personal media (photos, videos, music files).

If you decide to go for a repair install, follow the instruction on this guide (here) to learn how to do it (even if you don’t have an installation media.

Источник

[5 FIXES] Access Can’t Be Started Unable To Initialize The Windows Registry Error

Was unable to initialize the Windows Registry.

Rerun Microsoft Access or Microsoft Office Setup to reinstall”

There is another problem with Access 2010. Whenever I want to open it, the “Configuring Microsoft Office Professional 2010” window appears. This loses much time. I don’t have this problem with Outlook, Word and Excel 2010.

After reading out the above user query you all must have guessed about today’s blog topic. Yes, in this post we will discuss this very commonly encountered Access can’t be started unable to initialize the windows registry error.

So try all the listed solutions to get rid of Microsoft Access can’t be started unable to initialize the Windows registry error.

Fix Microsoft Access Issues
Run a database Scan with Stellar Access Database Repair Tool to repair inconsistent Access database. After the scan is complete, the repair process will restore the database to its normal state fixing all the errors.

Error Detail:

Error name: Microsoft Office Access can’t be started
Error number: Error 7899
Description: Microsoft Office Access can’t be started.@Microsoft Office Access was unable to initialize the Windows Registry.@Rerun Microsoft Office Access or Microsoft Office Setup to reinstall Microsoft Office Access.@1@@185309@3.

You will get the following error message at the time of opening the MS Access application.

Microsoft Access can’t be started.

Microsoft Access was unable to initialize the Windows Registry.

Rerun Microsoft Access or Microsoft Office Setup to reinstall Microsoft Access.

Error Screenshot

Why You Are Getting Access Can’t Be Started Unable To Initialize The Windows Registry Error?

How To Fix MS Access Can’t Be Started Unable To Initialize The Windows Registry Error?

1# Restore Windows Registry:

2# Review The Loadappinit_Dlls Registry Key

Set the LoadAppInit_DLLs registry key must be set to 0, but another program may have changed its value.

3#Assign Appropriate Permissions

Follow the below steps to assign the appropriate permissions:

Access 2007:

Access 2010:

Note

You may encounter the permission problem from the GUID to the retail key. If you are getting the GUID permission problem, then repeat steps 4 to 10 on the retail key or on the 12.0 or 14.0 key.

4# Remove The Safety

It is the simplest and safest workaround to fix can’t Be Started Unable To Initialize The Windows Registry error. In this, you have to disable the UAC, and then use it as an administrative account.

Warning: This will degrade your system Windows security so be careful if you are performing this solution. Malware will automatically get installed in Windows XP and the previous version.

Now you can easily switch the MS Access versions because you must be in the older versions of Windows.

5# Use Run As Administrator

Make a shortcut for running each of your msaccess.exe files as an administrator. This will allows each of your Access versions to get register by itself on the start-up.

For making this setup, follow the below steps:

So whenever you start your Access application, you need to hit the continue option from the opened dialog box of User Account Control.

If you are an Access 2007 user then you don’t need to use the Run As Administrator option as you can use the normal shortcut.

Note: After doing such changes, just switch to some other version and come back to the previous one before your MS Access application register itself for the correct library.

Final Verdict:

If unfortunately due to this Microsoft Access was unable to initialize the Windows Registry error your database file gets corrupt or damaged. Due to which you can’t perform any task on the database file. In that case, I recommend you to go with the MS Access Repair & Recovery Tool. This recovery software is one of the best ways to get rid of any kind of errors and restore your damaged database without any backup.

Apart from that, don’t forget to share your experiences with us after trying the above-mentioned workarounds to fix Microsoft Access can’t be started error.

This software ensures seamless repair & recovery of ACCDB & MDB database and restores all objects including tables, reports, queries, records, forms, and indexes along with modules, macros, etc. Fix Microsoft Access issues now in 3 easy steps:

Источник

Windows was unable to load the registry (User Profile Service)

This happens every so often after someone else is logged on, then they log off, and another user logs on.

Problem starts here:

Log Name: Application

Source: Microsoft-Windows-User Profiles Service

Date: 4/21/2010 5:51:50 PM

Task Category: None

Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

2 user registry handles leaked from \Registry\User\S-1-5-21-3692011518-2094500946-738968334-1002:

Process 820 (\Device\HarddiskVolume3\Windows\System32\winlogon.exe) has opened key \REGISTRY\USER\S-1-5-21-3692011518-2094500946-738968334-1002\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers

Process 2140 (\Device\HarddiskVolume3\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-3692011518-2094500946-738968334-1002\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers

2 user registry handles leaked from \Registry\User\S-1-5-21-3692011518-2094500946-738968334-1002:

Then causes this:

Log Name: Application

Source: Microsoft-Windows-User Profiles Service

Date: 4/21/2010 5:53:47 PM

Task Category: None

Windows was unable to load the registry. This problem is often caused by insufficient memory or insufficient security rights.

The process cannot access the file because it is being used by another process.

Leading to this:

Log Name: Application

Source: Microsoft-Windows-User Profiles Service

Date: 4/21/2010 5:53:47 PM

Task Category: None

Windows cannot load the locally stored profile. Possible causes of this error include insufficient security rights or a corrupt local profile.

The process cannot access the file because it is being used by another process.

Log Name: Application

Source: Microsoft-Windows-User Profiles Service

Date: 4/21/2010 5:53:47 PM

Task Category: None

Windows has backed up this user profile. Windows will automatically try to use the backup profile the next time this user logs on.

Log Name: Application

Source: Microsoft-Windows-User Profiles Service

Date: 4/21/2010 5:53:47 PM

Task Category: None

Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.

This never used to happen. When this first happened, I just Ignored it. but now I am getting tired of having to reboot my computer to log on the my profile. I would appreciate if somebody could give me an answer.

Operating System: Windows Vista Home Premium x86

Processor: Intel Pentium D 3.00 GHz

Replies (14) 

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

I am sorry, but we can not read your post.

We can only go on your Header:

Try tapping F8 at startup, and from the list of startup selections, select Safe Mode by using UP Arrow Key to go there > then hit Enter.

Try a System Restore once there, to pick a Restore Point before your problem..

Click Start > Programs > Accessories > System Tools > System Restore > pick a different time > Next > etc

If the above does not work:

Fix a corrupted user profile

After you create the profile, you can copy the files from the existing profile. You must have at least three user accounts on the computer to complete these steps, including the new account you just created.

A temporary profile is loaded after you log on to a Windows Vista-based system

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.