Skip to main content

Solved Windows 10 20H2 update screen resolution issue: ultrawide monitor connected to Microsoft Surface Dock

 Today I received the Windows 10 version 20H2 update on my corporate Microsoft Surface. After rebooting I had screen resolution issues on my external Dell Ultrasharp 3419W ultrawide monitor which was connected to the Surface Dock. Instead of the 3440x1440 resolution my monitor started with a 1024x768 resolution. When I tried to change the resolution back to the 3440x1440 setting I noticed that the highest supported resolution was 1280x1024.

When I connected the monitor directly to the Surface the native resolution of 3440x1440 was back. Updating and removing the general monitor driver did not help either. When I downgraded back to Window 10 2004 the problem was gone and support for 3440x1440 was back on the Surface dock.

I finally figured out how to solve the issue between the Surface dock and Windows 10 20H2. I downloaded the official Dell driver for my monitor and changed the generic driver to this Dell U3419W driver. Then I reinstalled the Windows 10 20H2 feature update and when I rebooted the monitor connected on the Surface dock was still using the native 3440x1440 resolution.

Comments

Popular posts from this blog

CS8357: The specified version string contains wildcards, which are not compatible with determinism.

Today I was busy with creating a WCF service solution in Visual Studio Enterprise 2017 (15.9.2). In this solution I use a few C# class libraries based on .NET 4.7.2. When I compiled the solution I got this error message: Error CS8357: The specified version string contains wildcards, which are not compatible with determinism. Either remove wildcards from the version string, or disable determinism for this compilation The error message is linking to my AssemblyInfo.cs file of the Class library projects. In all the projects of this solution I use the wildcard notation for generating build and revision numbers. // Version information for an assembly consists of the following four values: // // Major Version // Minor Version // Build Number // Revision // // You can specify all the values or you can default the Build and Revision Numbers // by using the '*' as shown below: // [assembly: AssemblyVersion("1.0.*")] [assembly: AssemblyVersion("1.0.

Fixing HTTP Error 401.2 unauthorized on local IIS

Sometimes the Windows Authentication got broken on IIS servers so you cannot log in locally on the server. In that case you get the dreadfully error message HTTP Error 401.2 - Unauthorized You are not authorized to view this page due to invalid authentication headers. To fix this issue you can repair the Windows Authentication feature with the following PowerShell commands: Remove-WindowsFeature Web-Windows-Auth Add-WindowsFeature Web-Windows-Auth

Remove Azure DevOps Enterprise application record from Azure AD

If you want to delete an Azure AD tenant which contains an Azure DevOps Enterprise application record you will first have to remove this Enterprise application record. Removing the Azure DevOps Enterprise record will not succeed from the user interface because the delete button is greyed out. To remove the record follow these steps: Create a new Global Admin account in the directory you are trying to delete. Make sure you copy the temporary password. Start Windows PowerShell commandline and run: Install-Module -Name AzureAD . Once done run Connect-AzureAD . You will be prompted to login, login with the user you created and you will be asked to change your password. Run Remove-AzureADServicePrincipal -ObjectId [Object ID] to remove the Enterprise application record. Remove the Global Admin account you created. After the Azure DevOps Enterprise record is removed you can delete the Azure AD tenant.