With error 0x80004005 log

How to Fix “Error 0x80004005” on Windows?

Error 0x80004005 is translated as an unspecified error and is usually seen when the user cannot access Shared Folders, Drives, Virtual Machines, Microsoft Account changes, and also when the Windows Updates fails to install. Troubleshooting this issue depends on where and how the error message is being originated from and since the error does not specifically tells you what the actual problem is, even in the Microsoft Books it is defined as “Unspecified Error“.

Error 0x80004005: Causes and Solutions

Repair Corrupt System Files

Before attempting any of the methods in this guide we highly recommend using Restoro to scan and restore corrupt and missing files from here, and then see if the issue is fixed if not then chose the issue from the index above and follow instructions given.

1. Error 0x80004005 on a VirtualBox

It usually is the registry key that causes issues.

Hold Windows Key and Press R. Type regedit and Click OK

Go to the following registry path:

If this key exists, delete it and try again. If deleting the key does not help, then try disabling your antivirus.

If it still doesn’t works then:

Uninstall your antivirus, test it and then reinstall it.
Replace your antivirus with another such as AVG or Security Essentials.

2. Error 0x80004005 when accessing a Shared Drive/Folder

We will use regedit to create a LocalAccountTokenFilterPolicy Value.

Hold Windows Key and Press R

Type regedit and click OK

Navigate to the following path in regedit

For 32 bit system, create a new DWORD value called LocalAccountTokenFilterPolicy.
For a 64 bit system, make a QWORD (64-bit) called LocalAccountTokenFilterPolicy.

In either case, set the value to numeric 1 (meaning on), and remember to click OK.

Usually, the LocalAccountTokenFilterPolicy value gets created before you have a chance to set the data value; no problem, just double-click and modify the data from 0 to 1.

Once this is done, restart your computer and see if you can now access the shared drives or folders.

If the problem persists after following all of the steps above; then

Hold the Windows key and Press R, and type hdwwiz.cpl to open Device Manager. Select Network Adapters and then click View from menu, and choose View Hidden Devices. Expand Network Adapters, and if you see Microsoft 6to4 Adapters, then delete them all by right clicking and selecting Remove Device.

Once done, reboot your PC and then test.

3. Error 0x80004005 when Installing Windows 7 or Windows Server 2008 R2 SP1

Download and Run CheckSUR from here. After the System Update Readiness Tool has finished checking the components on the system, run SFC Scan.

4. E_FAIL (0x80004005) When Setting Up VirtualBox on Ubuntu

If you are trying to allocate more then 3GB of RAM to the VM then make sure that the host is a 64-bit system, and true hardware pass through is allowed (VT-x)

4.1 Failed to open a session for the virtual machine

On certain sessions on a VM (VirtualBox) you may see the following error.

To fix the issue, Open Network Center and choose Change adapter settings. Right-click your Virtualbox host-only adapter and select Properties. Enable “Virtualbox NDIS6 Bridget Networking Driver if it’s disabled, and test again. VirtualBox should start fine now. If not, Enable Virtualbox NDIS6 Bridget Networking Driver for every network adapter you have (Ethernet, WiFi…) and always uncheck the NDIS6 and test.

4.2 Uninstall Microsoft 6to4

In order to solve this issue, you should uninstall the Microsoft 6to4 devices from your task manager. Keep in mind that you might not see these devices because they are hidden by default. So, you will only see these once you turn on the Show hidden devices option.

Here are the steps for deleting these devices.

1. Hold Windows key and press R
2. Type devmgmt.msc and press Enter

1. Click View and select Show hidden devices

1. Double click Network Adapters
2. Right click the Microsoft 6to4 device and select Uninstall. Repeat this step for all the Microsoft 6to4 devices you see in the list

Once you are done, restart your computer. Your issue should be solved once you log in to your Windows again.

5. Error 0x80004005 When Extracting Files

If you’re getting this error while trying to extract or open .zip or .rar files, you have a few potential fixes at your disposal.

5.1 Try a different extracting utility

First, make sure the file is not password protected and your extractor utility is not equipped to handle password protected files. You can do this by downloading another utility like 7Zip and see if you are asked to provide a password when trying to open or extract the same .zip or .rar archive.

5.2 Method 2: Disable the real-time protection of your AV

Another possible cause is an overprotective 3rd party security suite. Under certain conditions, several 3rd party antivirus suite will block the extraction of zipped files. If you’re using an external 3rd party antivirus instead of the default security suite (Windows Defender), you can try temporarily disabling the real-time protection or shielding of your 3rd party AV and see if the issue is resolved.

In the event that you no longer encounter the 0x80004005 error, consider uninstalling your current 3rd party suite and going for a different security suite. If you want to avoid other conflicts like this one, consider going for the built-in security solution.

5.3 Re-registering jscript.dll and vbscript.dll

If the first two possible solutions have failed you, let’s try a different approach. Some users have managed to get it fixed by re-registering a couple of DLL (dynamic link libraries) in an elevated Command Prompt. To be more precise, this method will attempt to fix the issue by re-registering jscript.dll (a library used when running JScript) and vbscript.dll (a module containing API functions for VBScript). Here’s a quick guide on how to do this:

1. Press Windows key + R to open up a Run box. Then, type “cmd” and Ctrl + Shift + Enter and click Yes at the UAC (User Account Control) prompt to open up an elevated Command Prompt.
   
2. In the elevated Command prompt, type the following command and press Enter:
3. In the same elevated Command prompt, type the following command and hit Enter:
4. Restart your computer and see if you’re able to open or extract .zip or .rar files without receiving the 0x80004005 error.

Источник

With error 0x80004005 log

Вопрос

Recently, our SCCM administrator saw fit to remove the Configuration Manager client from my machine. He has been unable to get the client re-installed, and now he wants me to rebuild my system. I am of the opinion that this issue should be solvable with much less hassle, so I have decided to try resolving the issue myself. Here is what I have found:

Looking up my system in Configuration Manager and opening the Client Check Detail tab, I see «Verify/Remediate client prerequisites.» It also shows a result of «Remediation Failed» with an error code of 0x0320012d.

I then copied the client installation files to my machine and attempted to install the client from the local drive. Here is what the ccmsetup log showed (In the interest of brevity I am posting only the part of the log that I think might be relevant):

Failed to get assigned site from AD. Error 0x80004005 ]LOG]!>

GetADInstallParams failed with 0x80004005 ]LOG]!>

Couldn’t find an MP source through AD. Error 0x80004005 ]LOG]!>

No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue. ]LOG]!>

Failed to parse ‘»C:\Windows\ccmsetup\ccmsetup.exe» ‘ with error 0x80004005 ]LOG]!>

A Fallback Status Point has not been specified. Message with STATEID=’100′ will not be sent. ]LOG]!>

A Fallback Status Point has not been specified. Message with STATEID=’307′ will not be sent. ]LOG]!>

CcmSetup failed with error code 0x80004005 ]LOG]!> 2015″ component=»ccmsetup» context=»» type=»1″ thread=»5480″ file=»ccmsetup.cpp:10883″>

I did a search on some of the errors shown, and I found the article, which shows exactly the same errors in the same order.

The article suggests some solutions, but I have been unable to try all of them. For example, one solution requires knowing the site code, and I have been unable to determine our site code.

A subsequent attempt to install the client resulted in these entries in the log file:

CreateInstance of CLSID_BackgroundCopyManager failed with 8007042C. Unable to check BITS version ]LOG]!>

This operating system does not contain the correct version of BITS. BITS 2.5 or later is required. ]LOG]!>

CcmSetup failed with error code 0x8007042c ]LOG]!>

I know that BITS is a prerequisite, so I did some research on how to determine my version of BITS and found this article:

Using the instructions in the article I have determined that I have BITS 4.0. So I think that the BITS version issue is related more to the fact that BackgroundCopyManager was unable to check the version.

I also ran the WMIDiag utility from Microsoft, and it does find a lot of errors in WMI that it says could prevent WMI from working correctly, so maybe that is the problem. That log file is a mile long, but I can post it, or parts of it, if needed.

I think that I’ve gone about as far as I can on my own. I am looking for guidance on how to fix this issue. What would you suggest?

Ответы

I am definitely making progress. Further research into the 997 error turned up an article which recommended running the follow from the command line:

msiexec.exe /regserver

I also installed KB3000988 because that is the hotfix for the issues caused by update 2918614. After a reboot, I was able to get the Visual C++ 2010 Service Pack 1 Redistributable Setup package installed. I then ran ccmsetup.exe again, and this time it finished without errors. My machine can now be remote controlled, and it is getting software updates, so clearly I am back talking to the server.

Based on my research, for some people running the msiexec command made no difference, and for others installing the 3000988 hotfix made no difference. I did both, and then rebooted, and it appears that one of them resolved at least part of my issue, but I cannot say for sure which action fixed the problem with getting the Visual C++ 2010 package installed.

I still have one lingering problem. When my machine is viewed in Configuration Manager, on the Client Check Detail tab, it still shows error 0x80070643 and indicates, «Verify/Remediate Client Prerequisites.» I am hoping that at some point my machine will report in to the server and that information will be updated. I really don’t want to close this thread until that information gets updated, just to make sure there are not any remaining problems to be solved. Is there a way to force that information to get updated so that I can verify that Configuration Manager is no longer seeing a problem?

Все ответы

Your client is unable to connect to a ConfigMgr Management Point to get details to download the client files. Your ConfigMgr admin has gone over the top slightly by asking you to issue rebuild on your device for sure.

You may however need to go back to the admin and ask for the ConfigMgr install switches that they use to install the product as they may be specifying a MP to talk to and get policy or a sitecode. If they have set up ConfigMgr boundaries correctly for your device and they have extended the schema in AD then you would not need to add any switches to the install command — however this does not look to be the case so you need more info.

One question — is your device in a domain or is it a workgroup PC?

If domain then I would go back to the admin and tell them to make sure boundaries exist for the IP range or AD site that your device is in. Get the MP and Sitecode details then refer to this article for installing the client with the correct switches https://technet.microsoft.com/en-us/library/gg699356.aspx

If workgroup then you definitely need to get the MP details and add in the correct switches.

But to be honest your ConfigMgr admin really needs to get onto this and give you more info or look into the problem themselves.

Rebuild the machine. No way!

Cheers Paul | http://sccmentor.wordpress.com

• Предложено в качестве ответа Xin Guo Microsoft contingent staff 9 сентября 2015 г. 8:41

Thanks for the reply. My machine is in a domain.

I may have misstated things a bit when I said that the site admin removed the client from my machine. He was working with a less experienced tech, and it may have been that tech who removed the client. Regardless, the situation is that it got removed and we have not been able to get it re-installed.

Also, to follow up on the WMI errors that I got when I ran the WMIDiag utility, I did a bit more research on that and found this article:

The article contains a number of tests to help determine if the WMI repository is corrupt. I checked as many of the items in the article as I could, and from what I can see, it all looks good. I don’t see any of the listed errors in my Application log, I can run the get—cimclass commands without error, and the winmgmt /verifyrepository command comes back with, «WMI repository is consistent.»

However, I did notice one curious item. Per the article, I checked the objects.data file size and found it to be 16,464 KB. But I also noticed that the C:\Windows\System32\wbem folder contains two repository folders:

• repository
• repository.001 (The date on this folder is the same date as the last time my machine communicated with the SCCM server.)

I’m not sure that’s relevant, but I thought I would mention it just in case.

I will pursue your recommendations and will report back as soon as I can.

My apologies for not getting back to this sooner. Last week was hectic and this week I have family in town, so my time has been limited. It is at the top of my To Do list for next week.

Cheers Paul | http://sccmentor.wordpress.com

Okay, I have more information. I found that the site code and MP information can be found in the ccmsetup.log file, so I have that information now. There are entries showing the MP name retrieved, the number of MP records retrieved (1), along with the site version and site code. So I have the MP and site code details that you suggested I get.

With the site code information I ran the following command, based on information found on another forum:

The installation failed with error code 0x80070643. So I pulled up the log file and decided to do a search on «fail» and I found the following entries (I’ve condensed it down at there were a lot of other entries mixed in):

Item ‘i386/vcredist_x86.exe’ is applicable. Add to the list. ]LOG]!>

File ‘C:\Windows\ccmsetup\vcredist_x86.exe’ returned failure exit code 1603. Fail the installation. ]LOG]!>

Discovering whether item ‘i386/vcredist_x86.exe’ exists. ]LOG]!>

context=»» type=»1″ thread=»11104″ file=»manifest.cpp:553″>

Couldn’t find a product with MSI product code ‘‘ in the MSI database. ]LOG]!

Item i386/vcredist_x86.exe has not been installed yet. Put to pending install list. ]LOG]!>

Params to send FSP message ‘5.0.7958.1501 Deployment Error 0x80070643. Pre-req: vcredist_x86.exe’ ] LOG]!>

I suspect that last entry is a key piece of information, and it explains why Client Check Detail tab for my machine in CM shows, «Verify/Remediate client prerequisites.» My next step was to attempt running that file directly, and I learned that it is the Microsoft Visual C++ 2010 x86 Redistributable Setup. I got a dialog box indicating that the installation failed, and including a link to the log file. I opened the log file and found the following:

Log File C:\Users\ \AppData\Local\Temp\Microsoft Visual C++ 2010 x86 Redistributable Setup_20150905_174116642-MSI_vc_red.msi.txt does not yet exist but may do at Watson upload time

Calling MsiInstallProduct(c:\7e905f593b70c6f67074d7538218f2\vc_red.msi, EXTUI=1

Returning IDOK. INSTALLMESSAGE_ERROR [Error 997.Overlapped I/O operation is in progress. ]

PerformOperation returned 1603 (translates to HRESULT = 0x80070643)

Action complete

OnFailureBehavior for this item is to Rollback.

Action complete

Action complete

[9/5/2015, 17:41:30]Final Result: Installation failed with error code: ( 0x80070643 ), «Fatal error during installation. » (Elapsed time: 0 00:00:14).

Note that the error code highlight in red is the same error code with which the ccmsetup.exe fails. So I would say this is the source of the error. Looking in Programs and Features on my machine I see that the x64 and x86 versions of the Microsoft Visual C++ 2010 Redistributable (10.0.31319 for both) are installed.

Part of me wants to just uninstall Microsoft Visual C++ 2010 Redistributable — x86, and then run the ccmsetup.exe file again to see if that fixes the issue. But the last thing I want to do is go from the frying pan into the fire, so I decided to error on the side of caution and post the information here, and then wait for feedback.

I do have the full error logs available, and can post those if needed.

Also, I have not been able to get the following updates to install from the Windows update site, and they fail with the same 0x80070643 error code.

• Microsoft .NET Framework 4.5.2 for Windows 7 x64-based Systems (KB2901983)
• Security Update for Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (KB2538243)
• Update for Microsoft Visual Studio 2010 Tools for Office Runtime (KB3001652)

I feel as if I am getting close to cracking this one, and I’ve learned a lot along the way. Any help that you can offer will be greatly appreciated!

I did a bit more research on the 0x80070643 error and came across this article, which states that one of the most common causes of the error is the .NET framework.

The article contains a link to a .NET framework article on the Microsoft site, but that link is broken. It does, however, get you to the Microsoft site, so I did a search and turned up the following article that has some troubleshooting steps:

I’ve tried methods 1 and 2 from the article to no avail. Method 2 eventually resulted in a message indicating that the .NET Framework Repair Tool could not identify the issue, and it created a .CAB file on my desktop containing log files to send to Microsoft for further analysis, which I did. I am now considering trying method 3, which is uninstalling and reinstalling the .NET framework. However, I would prefer to do that as a last resort.

As always, any advice will be greatly appreciated!

This is an unusual thread as you’re not specifically the administrator for the ConfigMgr environment.

However given the details of the CCMSetup logfile, it would appear that autodiscovery is failing to discover the site information for the primary site.

When the CCMSetup executes it attempts to automatically discover the primary site management point, from there it downloads the CCMSetup files that it needs to complete the installation of the client. In your situation the auto discovery is failing.

This can be due to a number of reasons, however all of these reasons require knowledge and understanding of the ConfigMgr site configuration, which your ConfigMgr Admin would know of.

The alternative to using auto discovery is to pass the parameters of the Site and MP information to the CCMSetup.exe, you would need to get these details from your ConfigMgr Admin as well.

In either case, you won’t be able to progress the status of your client installation without further understanding of the ConfigMgr site configuration, I’d recommend that you work with your admin in this case.

That being said, its completely unnecessary to rebuild your machine

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Thanks for the reply.

Actually, I think it is discovering the site information. In the ccmsetup log file I find the following entries (Site info obfuscated just to be on the safe side):

The MP name retrieved is ‘ ‘ with version ‘7958’ and capabilities ‘

MP ‘ ‘ is compatible ]LOG]!>

Retrieved 1 MP records from AD for site ‘ ‘ ]LOG]!>

Retrived site version ‘5.00.7958.1000’ from AD for site ‘ ‘ ]LOG]!>

SiteVersion: 5.00.7958.1000 ]LOG]!>

Only one MP is specified. Use it. ]LOG]!>

I have confirmed that the MP name and site code found in the log file are correct for our site.

After posting the information about the 0x80070643 error and the .NET Framework, I started doing some research on the following error, encountered in the Microsoft Visual C++ 2010 x86 Redistributable Setup (See my September 6, 2015 post):

Returning IDOK. INSTALLMESSAGE_ERROR [Error 997.Overlapped I/O operation is in progress. ]

I found this article, which does not cover my exact situation, but which does have some interesting information nonetheless:

The article mentions that update 2918614 can cause problems with the Windows Installer. I verified that my machine does have update 2918614 installed, and I do see the 10997 MSI Installer errors in my Windows Application log. I considered removing that patch, but from what I have read online, that does not fix the issue in all cases, and in some cases it causes more issues, so I decided against that course of action for now. I tried the registry hack (Figured that would be easier to roll back than a hotfix), and it allowed me to get .NET Framework 4.5.2 installed. So the problem with getting the .NET Framework update installed is resolved.

However, I still am unable to install the Microsoft Visual C++ 2010 x86 Redistributable Setup, which seems to be what is preventing my ccm client installation. In reviewing the log file for the Visual C++ installation, I noticed a link to the installation log, and in that log I found these entries:

MSI (s) (DC:B0) [17:41:30:388]: SECREPAIR: Crypt Provider not initialized. Error:997

MSI (s) (DC:B0) [17:41:30:388]: SECUREREPAIR: Failed to CreateContentHash of the file: install.res.3082.dll: for computing its hash. Error: 997

MSI (s) (DC:B0) [17:41:30:388]: SECREPAIR: Failed to create hash for the install source files

MSI (s) (DC:B0) [17:41:30:388]: SECUREREPAIR: SecureRepair Failed. Error code: 3e5F9DC44B8

Action start 17:41:30: ProcessComponents.

MSI (s) (DC:B0) [17:41:30:389]:

Error 997.Overlapped I/O operation is in progress.

I have tried searching on some of those errors, but thus far have only come up with more sites referencing update 2918614, with not a lot more information other than to try removing it.

Источник