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.

Make steps conditional in multi-stage YAML pipelines

To make the switch from the graphical release pipelines in Azure DevOps I am missing two features. The first one is to be able to defer a deploy and the second one is to exclude certain deployment steps without the need for editing the YAML file.  The defer option is something Microsoft has to solve in their Azure DevOps proposition. It's a feature which you have in the graphical release pipeline but what they have not implemented yet in their YAML pipeline replacement. Approvals and certain gate conditions are implemented on the environment but the defer option is still missing .  Pipeline The conditional deployment option can be implemented with the help of runtime parameters and expressions . In the parameter section you define boolean parameters which will control the deploy behavior. With the expressions you can control which stage/job/task should be executed when the pipeline runs. In the below YAML sample I experimented with conditions in the azure-pipelines.yml  file

Azure DevOps YAML based CD pipeline with multiple artifacts

In my post called " Switch from Azure DevOps release pipeline to YAML based CI/CD pipeline " I explained how to implement a combined CI/CD pipeline based on YAML templates. Because most of the deployments in my daily work are consuming multiple artifacts I had to do some additional R&D to find a solution for those releases in Azure DevOps. Base structure In the first post about the transition to YAML CI/CD pipelines I introduced the base structure. The templates I want to reuse are added to the yaml-template folders in the root of my GIT repo. For the CD pipelines which lack a CI phase I introduce a new folder called yaml-releases which will contain the YAML files for releases which are based on multiple artifacts. The folder structure within my GIT repo is thus: yaml-releases releaseArea myMultipleArtifactsRelease azure-pipelines.yml cd-job.yml yaml-templates jobs ... templates ...