Share via

How do I repair event ID 7023 in Windows 10?

  • Article

Question

Wednesday, January 6, 2016 10:53 PM | 1 vote

I have a problem with Microsoft Passport Container Service. The problem causes a boot time of about two hours as Microsoft Passport service waits for a response from Microsoft Passport Container service. During the time the system is booting it is not accessible from the console but can be accessed remotely through Remote Desktop. I am also unable to create accounts and there is no option for me to create a PIN for alternate login. In fact there are several areas of the user account controls that cannot be accessed.

I have an error in my Windows 10 event log indicating as follows:

"The Microsoft Passport Container service terminated with the following error: General access denied error"

The details show:

- System 

  - Provider 

   [ Name]  Service Control Manager 
   [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4} 
   [ EventSourceName]  Service Control Manager 

  - EventID 7023 

   [ Qualifiers]  49152 

   Version 0 

   Level 2 

   Task 0 

   Opcode 0 

   Keywords 0x8080000000000000 

  - TimeCreated 

   [ SystemTime]  2016-01-06T16:09:56.522120900Z 

   EventRecordID 1447 

   Correlation 

  - Execution 

   [ ProcessID]  1016 
   [ ThreadID]  2920 

   Channel System 

   Computer xxx1 

   Security 


- EventData 

  param1 Microsoft Passport Container 
  param2 %%2147942405 
   4E0067006300430074006E0072005300760063000000 




Binary data:


In Words

0000: 0067004E 00430063 006E0074 00530072 
0010: 00630076 0000   


In Bytes

0000: 4E 00 67 00 63 00 43 00   N.g.c.C.
0008: 74 00 6E 00 72 00 53 00   t.n.r.S.
0010: 76 00 63 00 00 00         v.c...

When I try to start the Passport Container Service, I get this error:

Windows could not start the Microsoft Passport Container Service on Local Computer.

    Error 0x80070005: Access is denied.

This sounds like some sort of permissions problem. I have reinstalled Windows (not a clean install) which didn't fix it. I have run sfc /scannow and Dism /Online /Cleanup-Image /RestoreHealth but it didn't help. How do I repair this system?

Rob Miller

All replies (12)

Tuesday, January 12, 2016 10:23 PM ✅Answered | 2 votes

This repaired my problem: http://www.tweaking.com/content/page/windows_repair_all_in_one.html

Rob Miller

Wednesday, January 6, 2016 11:34 PM | 1 vote

Try to repair Windows 10 using DISM : 
http://www.tenforums.com/tutorials/7808-dism-repair-windows-10-image.html

Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Wednesday, January 6, 2016 11:58 PM | 1 vote

If you read my post all the way to the bottom you'll see that I already did that.

Rob Miller

Thursday, January 7, 2016 7:04 AM | 2 votes

Hi Rob,

Based on your error message, it's indeed the permission issue.

Please make sure you logon with account have administrator right and take ownership of this service as below:

1. Open the Registry Editor.

2. Located to

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NgcCtnrSvc

3. Right click this entry, select Permission....

4. Add your current user account to group and give it full control permission.

5. Alternatively, click the Advanced, besides Owner, click the Change to take ownership.

After that, start the service again to check the result.

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Thursday, January 7, 2016 3:39 PM | 1 vote

I have already done this.

1. I tried changing ownership but it didn't make a difference so I changed it back to SYSTEM.

2. My current user account has full permissions, HOWEVER I did not check the box marked "Replace all child object permission entries with inheritable permission entries from this object."

3. Neither of these changes made a difference.

Rob Miller

Monday, January 11, 2016 9:09 AM | 1 vote

Hi,

If so, let's try to import the same key from other same version and architecture computer that works fine to see if it could resolve the issue.

Meanwhile, run these commands to fix the corrupted system files:

sfc /scannow

https://support.microsoft.com/en-us/kb/929833

Dism /Online /Cleanup-Image /RestoreHealth

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Monday, January 11, 2016 3:26 PM

Do any of you people ever take the time to actually read the post before responding? Can't you see that I've already done these things?

Rob Miller

Tuesday, January 12, 2016 9:57 PM

Try a Refresh. 

Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Wednesday, March 23, 2016 9:30 PM

+1 for the solution!

Thanks for the link! I was skeptical on using 3rd party software, but this was THE solution that also have worked for me (I'm sure I am exaggerating for there might be a simpler solutions, but time is money, and I needed to work, though this took away about 1.5 hours running in background).  I've tried all the fixing of regedit, powershell, etc which MSDN and TechNet offered/suggested, including this OP question...

Just a side note, though I could not login from the desktop (physically), I too was able to Remote Desktop into my Windows 10 (Enterprise) via domain credentials from my laptop, and run this tweaking.com.  It's the same domain account, so I don't think it was anything to do with credential/auth - it was just stuck in the login (did not even give me the opportunity to enter my local and/or domain credentials).

Sunday, September 4, 2016 8:29 AM

Hi Rob,

Based on your error message, it's indeed the permission issue.

Please make sure you logon with account have administrator right and take ownership of this service as below:

1. Open the Registry Editor.

2. Located to

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NgcCtnrSvc

3. Right click this entry, select Permission....

4. Add your current user account to group and give it full control permission.

5. Alternatively, click the Advanced, besides Owner, click the Change to take ownership.

After that, start the service again to check the result.

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Thank you! That's solution!.........error is back again!

The Microsoft Passport Container service terminated with the following error:
General access denied error.

Tuesday, February 28, 2017 9:59 PM

This repaired my problem: http://www.tweaking.com/content/page/windows_repair_all_in_one.html

What were the steps you used in the Repair section of tweaking?

Wednesday, August 9, 2017 8:18 AM

In my case error ID 7023 was being generated on the back of 'WMI Performance Adapter service termibated'. Resetting performance counter fixed my issue:
Open CMD as Admin, Type Lodctr /r. You should get a message that it's repaired from a backup. You might see errors in the event logs but they stop after 10-15 minutes.