How to: Resolve Windows error 0x8004FE33 indicating client activation failure
How to: Resolve Windows error 0x8004FE33 indicating client activation failure
I’ve been having a few issues with my SharePoint 2013 installation which has forced me to dive into the event log to see what possible errors might be occurring. One of those was error 0x8004FE33. It turns out this had nothing to do with my problems, it was simply Windows complaining it could not automatically active Windows Server. As I am reinstalling left and right servers as sometimes installations fail (how complex have they gotten that they don’t work on the first try as before) I have not given them Internet access and hence the error appears. Below is more information on how to resolve this issue if you are having problems activating your windows product. Most likely than not it is an internet connectivity issue.
Below are some of the error messages you may run across:
License acquisition failure details.
hr=0xC004C003
(or)
Acquisition of End User License failed. hr=0xC004C003
Sku Id=7d7240c9-5ea0-4a33-8061-a5f44d061f2e
(or)
License Activation (slui.exe) failed with the following error code:
hr=0xC004C003
RuleId=31e71c49-8da7-4a2f-ad92-45d98a1c79ba;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=7d7240c9-5ea0-4a33-8061-a5f44d061f2e;NotificationInterval=1440;Trigger=UserLogon;SessionId=1
- Windows 8
- Windows 7
- Windows Vista
- Windows Server 2012
- Windows Server 2008 R2
- Windows Server 2008
Additionally, you may experience one or more of the following symptoms:
- Activation fails and generates error code 0x8004FE33.
- The following Error events are recorded in the Application log:
Log Name: Application Source: Software Licensing Service Event ID: 8198 Level: Error Description: License Activation (SLUI.exe) failed with the following error code: 0x80004005Log Name: Application Source: Software Licensing Service Event ID: 1008 Level: Error Description: Acquisition of Secure Processor Certificate failed. Status Code=hr=0x8004FE33
- Activation fails, and you are not prompted for credentials.
Cause
If the proxy server is configured for Basic authentication, the server requires that you type a username and a password. However, the activation user interface does not let you enter these credentials. Therefore, the Basic authentication fails, and activation fails.
Workaround
General users
Method 1: Use the telephone to activate Windows
Start the Windows Activation Wizard to use the automated telephone system and activate Windows. To start the wizard, click Start, click Run, type SLUI 04, and then click OK.
If you are running Windows 8, follow these steps:
- Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search.
- Type SLUI 04, and then tap or click the displayed icon to open the wizard.
Advanced users
This method is intended for advanced computer users. If you are not comfortable with advanced troubleshooting, you might want to ask someone for help or contact support. For information about how to contact support, visit the following Microsoft website:
Method 1: Configure the proxy server to disable Basic authentication
For information about how to perform this method, see the documentation that is included with the proxy software.
Method 2: Configure your proxy server to exclude the URLs for the certificate revocation lists (CRLs) from the requirement for Basic authentication
To do this, configure the following list of CRLs to be unauthenticated on the proxy server:
- http://go.microsoft.com/
- https://sls.microsoft.com/
- https://sls.microsoft.com:443
- http://crl.microsoft.com/pki/crl/products/MicrosoftRootAuthority.crl
- http://crl.microsoft.com/pki/crl/products/MicrosoftProductSecureCommunications.crl
- http://www.microsoft.com/pki/crl/products/MicrosoftProductSecureCommunications.crl
- http://crl.microsoft.com/pki/crl/products/MicrosoftProductSecureServer.crl
- http://www.microsoft.com/pki/crl/products/MicrosoftProductSecureServer.crl
- https://activation.sls.microsoft.com
For information about how to perform this method, see the documentation that is included with the proxy software.
Love
Can we use Let's Encrypt, the free and open certificate authority?
Hola! gracias por la info, me sirvió el comando sacandole el nombre del server. En mi caso, fue una migración…
Yes 3rd option helped me too. I removed the WC key Values from config file then started working.
I know this is from 2014. But really, thank you!