Start Button is not working in Windows Server 2019

Question

Hi

We have a Windwos Server 2019 in which the "Start Button" failed to work for new users except for the previous old users.

We have verified the permission of the Start Folders and repective registry value as well.

But the said button works as expected when we login with any old accounts irrespective of type user or administrator.

Since the VM hosted in Azure environment, we have restroed the VM from a healthy backup which is 1 month Old. But still the issue persists.

Please need help me resolve this issue.

Answer 1

Hi, This is a particularly stubborn issue, and the fact that it persists even after restoring from a backup is a critical clue. It indicates the problem is likely not a simple file corruption, but rather a deeper issue with the user profile template or a system-wide component that the backup also contained.

The core of the problem lies in the difference between "old" user profiles (which work) and "new" user profiles (which don't). New profiles are created based on the Default User Profile. If this template is corrupted, all new users will inherit the same problem.

Here is a structured diagnostic and repair plan. Please follow these steps in order.

Step 1: Rule Out Profile-Specific Corruption First, let's test if the issue is truly universal for all new users or if it's specific to how they are created.

Create a brand new local user account and add it to the Administrators group.

Log out completely and log in with this new administrator account.

Test the Start Button:

If it works, the issue is likely with specific user group policies or permissions applied to your standard users.

If it does not work, this confirms a system-level corruption, and we proceed to Step 2.

Step 2: Rebuild the Corrupted Default User Profile Since old profiles work, we can use a working profile to rebuild the broken default template.

Log in with one of the "old" user accounts where the Start Menu works correctly.

Open File Explorer and navigate to C:\Users. You should see the folders for the old users and a Default folder.

Go to Control Panel > System and Security > System > Advanced system settings (on the left).

In the User Profiles section, click the Settings... button.

You will see a list of profiles stored on the computer. Select the profile of the "old" user that is working correctly.

Click Copy To....

In the "Copy profile to" field, type C:\Users\Default.

Click the Change... button under "Permitted to use," type Everyone, and click OK.

Click OK to start the copy. You will be prompted to overwrite the existing Default folder; confirm yes.

Restart the server.

Step 3: Investigate System-Wide Components If the previous step fails, the corruption is deeper. We need to check core system components.

Run System File Checker & DISM:

Open an Administrative Command Prompt.

Run the following commands, waiting for each to complete:

cmd dism /online /cleanup-image /restorehealth sfc /scannow These commands will check and repair corrupted protected system files.

Check for Rogue Policies with Procmon:

Download Process Monitor from Microsoft Sysinternals.

Reproduce the issue by logging in as a new user.

In Procmon, look for "ACCESS DENIED" results when StartMenuExperienceHost.exe or ShellExperienceHost.exe are trying to access files or registry keys. This can pinpoint a specific permission block that group policy might be enforcing.

Step 4: The Nuclear Option (if all else fails) If the above steps do not resolve the issue, the most reliable path is to create a new, clean Windows Server 2019 VM in Azure and migrate your roles and services. Given the time already invested, this may ultimately be faster and provide a more stable foundation.

The persistence of this issue across a backup restore is highly unusual and suggests a deep-seated corruption. The "Copy Profile" method in Step 2 has the highest success rate for this specific symptom.

I hope this structured approach helps you resolve this challenging issue.

If this guidance was helpful in diagnosing or resolving the problem, please feel free to mark it as "Accept Answer" 😊.

Best regards, VP

Answer 2

Hi Sheik Mohamed Yasar,

I have reviewed the event logs. This suggests a deeper issue with the AppX package deployment or registration process, which is critical for the Start Menu functionality.

Given that the previous steps did not resolve the issue, and considering this is a Windows Server 2019 instance with Remote Desktop Services (RDS), the problem may be compounded by RDS-specific configurations or a corrupted AppX subsystem. Here’s an updated approach that you can try:

Verify AppX Package Integrity: The errors point to a failure in registering AppX packages. Let’s manually re-register these components.

Open an Administrative PowerShell session.

  Run the following command to re-register all built-in Windows apps: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
  
     After completion, restart the server and test with a new user account.
     
     **Check RDS Profile Settings**: Since this is an RDS environment, the user profile loading process might be affected by RDS policies or profile management.
     
        Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System in the Registry Editor.
        
           Look for any entries related to ShellExperienceHost or Cortana that might be enforcing restrictions. If present, consider temporarily disabling them or consulting your group policy settings.
           
              Ensure the RDS profile path (if customized) is correctly set and not pointing to a corrupted template.
              
              **Repair Windows Store Components**: The Start Menu relies on Windows Store components, which might be corrupted.
              
                 Open an Administrative Command Prompt.
                 
                    Run: wsreset.exe
                    
                       This will reset the Windows Store cache. Restart the server afterward and test again.
                       
                       **Advanced Troubleshooting with Event Logs**: The recurring Event ID 5961 errors suggest a persistent deployment issue. Enable detailed logging for AppX deployment:
                       
                          Open Event Viewer and navigate to Applications and Services Logs > Microsoft > Windows > AppxDeployment-Server.
                          
                             Enable logging if it’s disabled, reproduce the issue, and review the logs for more specific error codes or clues.
                             
                                Share these logs with me if the issue persists for further analysis.
                                

If the above steps do not resolve the issue, the corruption might be embedded in the system image itself, possibly due to an Azure-specific update or patch applied post-backup. In that case, I recommend creating a new Windows Server 2019 VM from a fresh Azure Marketplace image, configuring RDS, and migrating your existing roles and data.

Hope it helps!! If it does, please accept the answer so that others can benefit too. If not, please let me know further. :)

Answer 3

Hi Sheik Mohamed Yasar,

How was everything? Have you solved it yet? If you haven't, I think the last resort is to access the official Microsoft Support for Business contact portal at this URL: https://support.microsoft.com/en-us/contactus/

This is the central hub for all business product support. Once on the page, you will be guided through a few steps to get the specific contact details for your issue:

Describe your problem: You can enter keywords like "legacy volume licensing activation."

Select a product: Choose the relevant product, such as "Windows" or "Microsoft 365."

Get support options: The website will then present you with the most up-to-date contact methods for your region, which often includes a direct phone number for commercial support.

I think this kind of support would facilitate you more easily, as it is a live chat that provides you with simultaneous consultancy.

If you find this information helpful to some extent, please accept the answer so that it could be spread further to those in need. Thank you and good luck :)

Vivian