Forum Widgets
Latest Discussions
Windows Server 2019 Administrator access gone
I recently was using Windows Server 2019 Evaluation version, everything working great. Then purchased full license and upgraded it with the license. Now I am unable to do anything because the Administrator account is inaccessible. I can't even restart the server without having to power off. Any help would be appreciated.aabahazieJun 14, 2025Copper Contributor12Views0likes0CommentsWindows Admin Center fail to work after installing June cumulative update
I installed June cumulative update patch in 11/6 Log Name: System Source: Microsoft-Windows-WindowsUpdateClient Date: 2025/6/11 10:14:09 Event ID: 43 Task Category: Windows Update Agent Level: Information Keywords: Started, Installed User: SYSTEM Computer: DC-MASTER.test.microbin.cn Description: Installation Started: Windows has started installing the following update: 2025-06 Cumulative Update for Microsoft server operating system version 24H2 for x64-based systems (KB5060842) Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945a8954-c147-4acd-923f-40c45405a658}" /> <EventID>43</EventID> <Version>1</Version> <Level>4</Level> <Task>1</Task> <Opcode>13</Opcode> <Keywords>0x8000000000002008</Keywords> <TimeCreated SystemTime="2025-06-11T02:14:09.6577485Z" /> <EventRecordID>125631</EventRecordID> <Correlation /> <Execution ProcessID="22092" ThreadID="27544" /> <Channel>System</Channel> <Computer>DC-MASTER.test.microbin.cn</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="updateTitle">Applies to x64-based 2025-06 Cumulative Update for Microsoft server operating system version 24H2 of the system (KB5060842)</Data> <Data Name="updateGuid">{dc616f05-dd63-47e3-9365-ff4bc05397eb}</Data> <Data Name="updateRevisionNumber">1</Data> </EventData> </Event> and after restarting OS and get ApplicationError of Windows Admin Center. Starting the Windows Admin Center service and went to browser then get error "ERR_CONNECTION_CLOSED". Log name: Application Source: Application Error Date: 2025/6/11 10:32:31 Event ID: 1000 Task Category: Application Crash Event Level: Error Keywords: User: SYSTEM Computer: DC-MASTER.test.microbin.cn Description: Faulting application name: WindowsAdminCenterAccountManagement.exe, version: 2.4.2.1, time stamp: 0x674f0000 Faulting module name: KERNELBASE.dll, version: 10.0.26100.4061, time stamp: 0xe6128e90 Exception code: 0xe0434352 Error offset: 0x00000000000c9f0a Faulting process ID: 0x2B94 Faulting application start time: 0x1DBC4776EBA8992 Faulting Application Path: C:\Program Files\WindowsAdminCenter\Service\WindowsAdminCenterAccountManagement.exe Faulting Module Path: C:\WINDOWS\System32\KERNELBASE.dll Report ID: 91c0debe-943e-426b-a15b-646e6545e2ba Faulting Package Full Name: Faulting Package Relative Application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2025-06-11T02:32:31.6246703Z" /> <EventRecordID>772255</EventRecordID> <Correlation /> <Execution ProcessID="31216" ThreadID="31368" /> <Channel>Application</Channel> <Computer>DC-MASTER.test.microbin.cn</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="AppName">WindowsAdminCenterAccountManagement.exe</Data> <Data Name="AppVersion">2.4.2.1</Data> <Data Name="AppTimeStamp">674f0000</Data> <Data Name="ModuleName">KERNELBASE.dll</Data> <Data Name="ModuleVersion">10.0.26100.4061</Data> <Data Name="ModuleTimeStamp">e6128e90</Data> <Data Name="ExceptionCode">e0434352</Data> <Data Name="FaultingOffset">00000000000c9f0a</Data> <Data Name="ProcessId">0x2b94</Data> <Data Name="ProcessCreationTime">0x1dbc4776eba8992</Data> <Data Name="AppPath">C:\Program Files\WindowsAdminCenter\Service\WindowsAdminCenterAccountManagement.exe</Data> <Data Name="ModulePath">C:\WINDOWS\System32\KERNELBASE.dll</Data> <Data Name="IntegratorReportId">91c0debe-943e-426b-a15b-646e6545e2ba</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event> Log name: Application Source: Application Error Date: 2025/6/13 10:02:59 Event ID: 1000 Task Category: Application Crash Event Level: Error Keywords: User: NETWORK SERVICE Computer: DC-MASTER.test.microbin.cn Description: Faulting application name: WindowsAdminCenter.exe, version: 2.4.2.1, time stamp: 0x674f0000 Faulting module name: KERNELBASE.dll, version: 10.0.26100.4202, time stamp: 0xfc5b8f29 Exception code: 0xe0434352 Error offset: 0x00000000000c85ea Faulting process ID: 0x75C8 Faulting application start time: 0x1DBDC0748F8CFA8 Faulting Application Path: C:\Program Files\WindowsAdminCenter\Service\WindowsAdminCenter.exe Faulting Module Path: C:\WINDOWS\System32\KERNELBASE.dll Report ID: 80f0b279-ffe4-4584-ac22-cb879fe49864 Faulting Package Full Name: Faulting Package Relative Application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2025-06-13T02:02:59.6057841Z" /> <EventRecordID>793400</EventRecordID> <Correlation /> <Execution ProcessID="15432" ThreadID="11684" /> <Channel>Application</Channel> <Computer>DC-MASTER.test.microbin.cn</Computer> <Security UserID="S-1-5-20" /> </System> <EventData> <Data Name="AppName">WindowsAdminCenter.exe</Data> <Data Name="AppVersion">2.4.2.1</Data> <Data Name="AppTimeStamp">674f0000</Data> <Data Name="ModuleName">KERNELBASE.dll</Data> <Data Name="ModuleVersion">10.0.26100.4202</Data> <Data Name="ModuleTimeStamp">fc5b8f29</Data> <Data Name="ExceptionCode">e0434352</Data> <Data Name="FaultingOffset">00000000000c85ea</Data> <Data Name="ProcessId">0x75c8</Data> <Data Name="ProcessCreationTime">0x1dbdc0748f8cfa8</Data> <Data Name="AppPath">C:\Program Files\WindowsAdminCenter\Service\WindowsAdminCenter.exe</Data> <Data Name="ModulePath">C:\WINDOWS\System32\KERNELBASE.dll</Data> <Data Name="IntegratorReportId">80f0b279-ffe4-4584-ac22-cb879fe49864</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event> Even reinstalled and that won't work. Before install June cumulative update Windows Admin Center works fine and no error happened.MicrocharonJun 14, 2025Copper Contributor89Views0likes1CommentHow do I create a new certificate for Windows Admin Center??
I just now observed that our internal WAC certificate was only two months old and it's already expired. Can I simply create and use our own self-signed certificate and use it?? Do I install it like normal certificates within the Certificates MMC and WAC will automagically use it?? Thank you, Tomtlyczko2Jun 10, 2025Copper Contributor92KViews0likes25Commentswinpty error accessing powershell tab
WAC Ver: 2.4.1 running on Windows Server 2022 I can access and perform all other WAC functions on the remote connected server (Win 2022) but when I try to access the powershell tab and click 'connect' I am met with a "Session End: click 'Connect' to reconnect." error. Clicking 'Connect' just cycles the same error. The windows event log error is as follows: Category: Microsoft.WindowsAdminCenter.Common.ServiceLog EventId: 414 SpanId: d138bcb891359bec TraceId: f373ad4711a131524c5c01e8b6a2e591 ParentId: bb6d22e32ab6da73 ConnectionId: 0HND3HPV5LDCV RequestId: 0HND3HPV5LDCV:00000001 RequestPath: /api/PseudoConsole/nodes/fakeservername.com/powershellconsole ActionId: b3f1dbd0-b87e-49e5-a13d-ba66e8d18af1 ActionName: Microsoft.WindowsAdminCenter.Controllers.PseudoConsole.PseudoConsoleController.PowerShellConsole (Microsoft.WindowsAdminCenter.Controllers.PseudoConsole) Failed to open winpty (8), Columns=194, Rows=44 The internal windows firewall is turned off completely, and outside of WAC, initiating a "Enter-PSSession -ComputerName" command in powershell verison 7.5.1 works fine, I can run commands on the remote server from there. Any ideas?jwsys00Jun 05, 2025Copper Contributor26Views0likes0CommentsWindows Admin Center 2410: cannot add computers
After a fresh installation of Windows Admin Center 2410, I cannot add any servers, clusters, PCs etc. WAC gives me "You can add this computer to your list of connections, but we can't confirm it's available" when I enter a computer name (either of FQDN or computer name alone). When I change to the Search Active Directory tab, I get: "We can’t search Active Directory because the Windows Admin Center computer isn’t joined to an Active Directory domain. It’s also possible that your account doesn’t have permission to read from Active Directory." The account I use is a domain admin, and the server running WAC is definitely joined to the AD DS. The server had the previous version of WAC installed where everything worked. Now, with the new version, that's no longer the case...ahinterlJun 03, 2025Copper Contributor6.3KViews10likes20CommentsMandatory AccessKey parameter for Import-WACConnection Powershell cmdlet in 2410
Hello, I have recently updated to Admin Center 2410, needed to do a fresh install because I ran into some Ajax error 500 problems when I dried to updrade the existing installation. Now I had a script running one a week which fetched all AD computers and Clusters and imported them as shared connection. I have already figured that I need to use a different path to import the Microsoft.WindowsAdminCenter.ConnectionTools module, and that the syntax for Import-Connection is now Import-WACConnection. However, when trying to connect, the commandlet now has a mandatory AccessKey parameter. The help suggests: "-AccessKey <String> The access key to the endpoint for form login. The access key can be created from Advanced menu of Settings on Windows Admin Center UI." However, I cannot find that option in the UI, there is only "Advanced" in the Development section of the UI, and there is no option for generating an access key. P.S. I have installed WAC to use Kerberos integrated Windows Authentication. In the past, the Import-Connection CMDlet was also just using the credentials of the currently logged-on user. Thank you for your help, MarcMa-PoMay 29, 2025Copper Contributor769Views0likes11CommentsWindows Admin Center.exe exception (0xe0434352)
I have installed an Azure Local 23H2 one-noded stack and enabled Windows Admin Center (Preview) extension via Azure portal. Solution version: 10.2503.0.13 Node OS Build: 25398.1486 Node Azure Arc Agent version: 1.46.02809.1841 however the WindowsAdminCenter service on the node will not start: Extension Message: Executing Enable operation, SettingDnsRecords: Creating/updating DNS records, GetDataFromMetadataService: Getting data from Azure metadata service, GetInstanceMetadataForArc: Retrieving the virtual machine instance metadata information, GettingWacPort: Getting Windows Admin Centers configured port, GettingCSPFrameAncestors: Getting Windows Admin Center configured CSP frame ancestors, UpdatingWindowsAdminCenterConfiguration: Updating Windows Admin Center Configuration, StoppingWindowsAdminCenterService: Stopping Windows Admin Center service, UpdatingInstallationTypeSettings: Updating Installation type for Windows Admin Center, UpdatingCSPSettings: Updating CSP Frame Ancestors for Windows Admin Center, UpdatingCORSSettings: Updating CORS origins for Windows Admin Center, UpdatingPort: Updating port for Windows Admin Center, UpdatingWebSocketValidationOverride: Updating WebSocket validation override settings, UpdatingTokenAuthenticationEnabled: Updating token authentication setting, UpdatingAutoUpdate: Updating auto update setting, SettingProxy: Updating proxy for Windows Admin Center, GettingWacPort: Getting Windows Admin Centers configured port, UpdatingWindowsAdminCenterConfiguration: Updating Windows Admin Center Configuration, GetDataFromMetadataService: Getting data from Azure metadata service, GetInstanceMetadataForArc: Retrieving the virtual machine instance metadata information, TestWACAppServiceReachability: Testing reachability of Application Web Service of Windows Admin Center, GetAccessTokenForArc: Getting access token from Azure Arc's identity endpoint, GetDataFromMetadataService: Getting data from Azure metadata service, GetInstanceMetadataForArc: Retrieving the virtual machine instance metadata information, WriteCertificateThumbprint: Storing certificate thumbprint for future reference., RetrieveCertificate: Retrieving certificate from key vault using app service, ImportingCertificate: Importing Certificate to Certificate Store, StoppingWindowsAdminCenterService: Stopping Windows Admin Center service, UpdatingSubjectName: Updating WAC certificate subject name, UpdatingCertificateACL: Updating WAC certificate ACL, UpdatingServicesEndpoints: Updating WAC endpoint FQDN, StartingWindowsAdminCenterService: Failed to start Windows Admin Center service In Event viewer (system) I can see that the service starts and then stops again right after with the following error: Windows Admin Center.exe exception (0xe0434352) I have tried to reboot node and remove and reinstall extension. But the error persists. I know it is in preview but I would like to get it to work. Any suggestions?SolvedChris_toffer0707May 23, 2025Iron Contributor94Views0likes2CommentsServer 2022 fresh installs, licensed, Date and Time reset to wrong time after each reboot.
The systems can access the internet just fine. I update the time zone to Central and the time does not change. I manually change it, then reboot and it's back to the wrong time. I also see the "Some of these settings are managed by your organization" in settings -> Date & Time. I should not see that in any area of these systems in my opinion. Windows Server 2022 V21H2 OS Build 20348.587. These are not company servers - they are in my home.jgkloekMay 22, 2025Copper Contributor11Views0likes0CommentsWindows Admin Center Credential Issue
Hi, I am using Windows Admin Centre installed on Windows 11 to connect (manage) a Windows 2025 server. Both machines are not in Active Directory so workgroup mode. So I need to connect as a specific user. The issue is the credentials are not saved so it reverts back to the credentials of the gateway machine (Windows 11). Is there a way I can get it to remember the credentials after I exit Admin Center? Thanks Wardwardh1760May 19, 2025Copper Contributor27Views0likes0CommentsExtended Network Extension it is not available in Windows Admin Center
According to this documentation https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/azure/azure-extended-network I would like to use Extended Network Extension but it is not available in Windows Admin Center that I installed on Windows 2022. Any idea? Special version of Windows Admin Center?MariuszFerdynMay 17, 2025Copper Contributor8Views0likes0Comments
Resources
Tags
- Windows Admin Center32 Topics
- WAC30 Topics
- Storage Migration Service12 Topics
- Admin Center7 Topics
- Active Directory6 Topics
- Windows Server6 Topics
- Group Policy5 Topics
- Error5 Topics
- azure4 Topics
- General3 Topics