utmapp / utmapp/UTM

Experimental 3D driver resolution issues

Open
#7,830 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
Swift
Stars
35.5k
Forks
1.8k
Avg merge
5d 5h
Merged PRs (30d)
7

Description

**Describe the issue**
I created a new Windows 11 ARM VM on my MacBook and used the built-in display for the VM setup. The VM is fully patched (19 August 2026) and uses the experimental 3D driver, installed with the latest UTM guest tools. I run the VM in windowed mode with 100% scaling (no Retina resolution)

A 2560 x 1440 external monitor is connected to the Macbook and configured as primary display.

The VM configuration uses the following Display settings:

Emulated card: virtio-ramfb-gl (GPU supported)
Resize display to windows size automatically: Checked
Upscaling: Nearest neighbor
Downscaling: Linear
Retina Mode: Unchecked

When I put the running VM in full screen on the built-in display, Windows scaling automatically scales to 125% and the resolution resizes correctly to 1512 x 949. However, Windows scaling should not be adjusted, it should keep 100%

Moving the running VM window on the external display (2550 x 1440), everything works as expected. No Windows rescaling happens.

When putting the running Windows VM to full screen, Windows scaling jumps to 150% and the resolution is set to 1512x952. Exiting full scrren and reactivating full screen now sets the scaling to 150% and resolution to 1920x1440. Doing this multiple times always results in 150% scaling and 1920x1440 resolution.

The VM never detects 2560x1440

Another strange thing happens whenever the VM has been put once in full screen. I switch back to window mode and shut down the VM. Instead of keeping the VM in window mode, the VM automatically switches to full screen during the shutdown process.

Hope this helps.

**Configuration**
* UTM Version: 5.04
* macOS Version: macOS Tahoe 26.6.2
* Mac Chip (Intel, M1, ...): Macbook M1 Pro

**Debug log**

[debug-scaling-windows-vm.log](https://github.com/user-attachments/files/31235958/debug-scaling-windows-vm.log)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the report's Windows 11 ARM VM configuration with the experimental 3D driver, then inspect debug-scaling-windows-vm.log. Verify behavior on the built-in and external displays in windowed and full-screen modes; done means Windows keeps the intended 100% scaling and detects the expected resolution without switching back to full screen during shutdown.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, swift
Domain
computer-graphics, desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.