JayInTech
Contributor
Contributor

Change display resolution Windows11 on M1

Hi,

I successfully got the Insider Program ARM64 preview of Windows 11 running on my M1 Macbook, even the internet.

Right now it's stuck in 1024x768 vga resolution.  Anyone with a tip on how I can get it to scale to 1920 x 1080 with the MIcrosoft Basic Display Adapter?

 

0 Kudos
27 Replies
Technogeezer
Virtuoso
Virtuoso

Since VMware does not provide VMware Tools for Windows on ARM (due to it being unsupported) there’s no way for Windows to directly resize the virtual graphics adapter resolution. Nor is there a Fusion setting to change the default.

The workaround is to RDP (e.g using Microsoft Remote Desktop app on the Mac) into the VM, which will allow resizing of the session. 

0 Kudos
Ahmed_1983
Contributor
Contributor

I still have same problem any body get soluation for this problem  

0 Kudos
Technogeezer
Virtuoso
Virtuoso

There is no solution as noted earlier in this thread.

if you are using Windows 11 Pro, the workaround of a Remote Desktop session into the virtual machine will let you  get a larger screen resolution. With Windows 11 Home you are out of luck since Microsoft does not allow Remote Desktop to be enabled for that version. 

0 Kudos
Ahmed_1983
Contributor
Contributor

I try to use Remote desktop   but I cant I showing message to me cant connent to other pc

0 Kudos
Technogeezer
Virtuoso
Virtuoso

Did you enable remote access in Windows Settings within the virtual machine ? It is off by default. 

0 Kudos
k_ronny
Enthusiast
Enthusiast

Hi,

it is possible, I run it with 1920x1200

Bildschirmfoto 2022-01-16 um 23.05.36.png

 

 

 

 

 

 

 

 

 

 

in Windows mount the ESP partition to e.g. "a:\"

Bildschirmfoto 2022-01-16 um 22.50.40.png

from an existing Debian installation copy the directories "/boot/grub" to "a:\" and "/boot/efi/EFI/debian" to "a:\EFI\"

Bildschirmfoto 2022-01-16 um 22.54.12.png

 

 

 

 

 

 

 

 

 

 

Bildschirmfoto 2022-01-16 um 22.53.31.png

the file "a:\efi\debian\grub.cfg" looks like this:

#
# minimal grub configuration
#

set timeout=2
set default=0

set gfxmode=1920x1200

menuentry "Windows 11" {
insmod gfxterm
terminal_output gfxterm
set bootnext=/efi/microsoft/boot/bootmgfw.efi
search --file $bootnext --set root
chainloader $bootnext
boot
}
# eof

the display resolution is set with "gfxmode=1920x1200"

delete the file "a:\grub\grub.cfg"

shutdown windows and restart into firmware - hold option (alt) key

Bildschirmfoto 2022-01-16 um 23.11.24.png

 

 

 

 

 

 

 

 

 

 

 

then follow this guide https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries (sorry this is for proxmox but also applies here) to add a new boot entry

Ahmed_1983
Contributor
Contributor

yes I do 

0 Kudos
xav0m3
Contributor
Contributor

Hi there,

Thank you for your input.

Unfortunately it doesn't work for me. Could you share which debian iso did you use as you can't file exactly the files you used and it seems when I change the boot config it doesn't start up.

Thanks

0 Kudos
k_ronny
Enthusiast
Enthusiast

Hi,

I had another look into it and it is even simpler. The only files you need are 'grubaa64.efi and 'grub.cfg'.

If you have mounted the ESP partition (mountvol a: /s) then your a: directory should look like this:

content of 'a:\'

A:\>dir
 Volume in Laufwerk A: hat keine Bezeichnung.
 Volumeseriennummer: BADD-D196

 Verzeichnis von A:\

16.01.2022  22:22    <DIR>          EFI
               0 Datei(en),              0 Bytes
               1 Verzeichnis(se),     72.183.808 Bytes frei

A:\>

content of 'a:\EFI\'

A:\EFI>dir
 Volume in Laufwerk A: hat keine Bezeichnung.
 Volumeseriennummer: BADD-D196

 Verzeichnis von A:\EFI

05.10.2021  00:13    <DIR>          .
05.10.2021  00:13    <DIR>          ..
05.10.2021  00:13    <DIR>          Microsoft
16.01.2022  22:15    <DIR>          Boot
24.02.2022  21:23    <DIR>          debian
               0 Datei(en),              0 Bytes
               5 Verzeichnis(se),     72.183.808 Bytes frei

A:\EFI>

content of 'a:\EFI\debian\'

A:\EFI\debian>dir
 Volume in Laufwerk A: hat keine Bezeichnung.
 Volumeseriennummer: BADD-D196

 Verzeichnis von A:\EFI\debian

24.02.2022  21:23    <DIR>          .
24.02.2022  21:23    <DIR>          ..
24.02.2022  21:23         1.814.528 grubaa64.efi
24.02.2022  21:23               213 grub.cfg
               2 Datei(en),      1.814.741 Bytes
               2 Verzeichnis(se),     72.183.808 Bytes frei

A:\EFI\debian>

The file 'grubaa64.efi' is included in this debian package:

https://deb.debian.org/debian/pool/main/g/grub2/grub-efi-arm64-bin_2.06-2_arm64.deb

I use this little shell script to download the right 'grubaa64.efi'. 

#! /bin/sh

current_path="$(pwd)"
current_ip="$(nslookup "$(hostname -s)" | sed -n -e '/Address/ s/.* //p')"

#
# 1) download
# -----------
#

mkdir "${current_path}"/debian
cd "${current_path}"/debian || {
	printf "%s\n" "== Could not create directory 'debian', bye."
	exit 1
}

curl -s -O https://deb.debian.org/debian/pool/main/g/grub2/grub-efi-arm64-bin_2.06-2_arm64.deb
tar -x -f grub-efi-arm64-bin_2.06-2_arm64.deb data.tar.xz
tar -x --to-stdout -f data.tar.xz usr/lib/grub/arm64-efi/monolithic/grubaa64.efi > grubaa64.efi
rm -f data.tar.xz grub-efi-arm64-bin_2.06-2_arm64.deb

#
# 2) create grub.cfg
# ------------------
#

cat > grub.cfg <<endOfFile
#
# minimal grub configuration
#

set timeout=2
set default=0

set gfxmode=1920x1200

menuentry "Windows 11" {
	insmod gfxterm
	terminal_output gfxterm
	chainloader /efi/microsoft/boot/bootmgfw.efi
	boot
}

# eof
endOfFile

cd "${current_path}"

cat <<endOfMessage

Now boot Windows in VMware Fusion.

Select:

   'Start' -> search for cmd.exe --> open as Administrator


Type:

   mountvol a: /s

   a:

   cd EFI

   scp -r ${USER}@${current_ip}:${current_path}/debian .


Select:

   'Start' --> shutdown


Now in VMware Fusion open 'Settings' of your Windows virtual machine

   'Settings' --> 'Startup Disk' --> OptionKey + 'Restart to firmware...'


Then

   'Boot Maintenance Manager' --> 'Boot Options' --> 'Add Boot Option'

   look for an entry with '.../HD(...' and select that entry

   '<EFI>' --> select that

   '<debian>' --> select that

   '<.>'
   '<..>'
   'grubaa64.efi' --> select that

   'Input the description' --> select that and type in a description

   'Commit Changes and Exit' --> select that

   'Boot Options' select that

   'Change Boot Order' --> select that

   'Change the order' --> select that

   with 'CursorUp' / 'CursorDown' you can select yor new entry
   with '+' / '-' you can reposition your new entry

   'Go Back To Main Page'

   'EscKey'

   Sometimes it will ask you to save your changes: type 'y'

   'Continue'


It should now boot to 'grub'
After 2s (you can change that in your 'debian/grub.cfg') it should boot your Windows.


endOfMessage

# eof

Hopefully this will help you.

xav0m3
Contributor
Contributor

Hey @k_ronny 

Works like a charm.

Thank you very much.

 

0 Kudos
ReinaldoA1
Contributor
Contributor

Hi everybody,

Unless there is another workaround, the whole point is that there are no VM tools for ARM64/Win11. Connecting through RDP is the only I found to map Mac's folders to my VM session. Apart from it, it's a bit slow sometimes and, the only problem I'm facing is Excel saving files with dates from year "2076" instead of 2022. I have no problem with other applications and even Excel files generated by other apps. Finally, the latest release earlier this week (19431034) did not solve this issue as well. 

Best regards

Reinaldo A

 

0 Kudos
cxdani
Contributor
Contributor

The method of k_ronny really works.

I used an ubuntu to extract the files from the deb package, so the commands from the script were not working for me.

I used command ar to extract all the files from the deb package:

ar vx grub-efi-arm64-bin_2.06-2_arm64.deb

then I just opened the file data.tar.xz with the default archive program and I extracted the file grubaa64.efi

I created manually grub.cfg

In Windows 11 VM I used WinScp to copy the two files from ubuntu to a temporary folder (Downloads\Temp for example).

After I mounted the ESP partition, I created the folder EFI\debian, I copied grubaa64.efi and grub.cfg from Downloads\Temp to EFI\debian, then I did all the rest of the steps to create and enable the new boot option, as described by k_ronny.

Thanks a lot k_ronny for this great hack.

 

0 Kudos
havihe
Contributor
Contributor

@k_ronny

wow, this works like a charm.

just registered to thank you.

0 Kudos
qwertyii
Contributor
Contributor

HI, I dont see the debian diredctory after Microsoft and Boot

 

0 Kudos
qwertyii
Contributor
Contributor

CAn I change it to 2560x1600

 

0 Kudos
k_ronny
Enthusiast
Enthusiast

If you have a running linux installation, you can ask 'grub' for the available resolutions.

At the 'grub'- menu type 'c' to get the 'grub'- command prompt.

Then type the command 'videoinfo' to get the available resolutions.

The currently selected resolution is marked with a '*'.

In my case it looks like this:

grub› videoinfo
List of supported video modes:
Legend: mask/position=red/green/blue/reserved
Adapter »EFI GOP driver«:
  0x000  320 x  200 x 32 (1280) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
  0x001  640 ×  480 x 32 (2560) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
  0x002  800 x  600 x 32 (3200) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
  0x003 1024 x  768 x 32 (4096) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
  0x004 1280 x 1024 x 32 (5120) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x005 1152 x  864 × 32 (4608) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x006 1280 x  960 × 32 (5120) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x007 1280 x 1024 x 32 (5120) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x008 1400 x 1050 x 32 (5600) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x009 1600 x 1200 x 32 (6400) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x00a 1792 x 1344 x 32 (7168) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  Ox00b 1856 x 1392 x 32 (7424) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  Ox00c 1920 x 1440 x 32 (7680) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  Ox0Od 1366 x  768 x 32 (5464) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  Ox00e 1680 x 1050 x 32 (6720) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
* Ox0Of 1920 x 1200 x 32 (7680) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x010 2048 x 1536 x 32 (8192) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x011  320 x  240 x 32 (1280) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x012  400 x  300 x 32 (1600) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x013  512 x  384 x 32 (2048) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x014  854 x  480 x 32 (3416) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x015 1280 x  720 x 32 (5120) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x016 1920 x 1080 x 32 (7680) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
  0x017 1280 x  800 x 32 (5120) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
  0x018 1440 x  900 x 32 (5760) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
  0x019  720 x  480 x 32 (2880) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x01a  720 x  576 x 32 (2880) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x01b  800 x  480 x 32 (3209) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
  0x01c 1280 x  768 x 32 (5120) Direct color. mask: 8/8/8/8 pos: 16/8/0/24
grub>

 

0 Kudos
ReinaldoA1
Contributor
Contributor

Hi everyone, 

I still can't see the point on adjusting the screen resolution and connecting directly to the VM without RDP if we cannot map any local folder on my Mac inside Windows 11 VM. Did anybody managed any workaround since we have no VMtools available? If not, is there a way other than connecting through RDP with folder redirection?

Best regards

 

0 Kudos
Technogeezer
Virtuoso
Virtuoso

Without an in-guest tools implementation there isn’t a way for that Windows 11 for ARM to use the Fusion shared folders implementation. There are no open source tools for Windows like open-vm-tools for Linux. 

Either RDP client folder mapping or configuring macOS SMB shares are options if you want shared folders between host and guests. 
If file transfer is what you need instead of a shared folder, then something like WinSCP might also be an option. 

This of course could change in the future. (Keeping fingers crossed that VMware has good news for us. @Mikero has has hinted about something coming in June but nothing specific on the Window situation, though). 

0 Kudos
ReinaldoA1
Contributor
Contributor

HI @Technogeezer,

Thanks again for your kind support, but I did all that was under my range (of knowledge) to capture my macOS SMB shared folders from my guest Windows 11 VM, but I failed. The SMB shared folders are recognized by another Windows 10 PC in the same network, but never by my Windows 11 ARM VM, even using a bridged connection and having everyone in the same workgroup. Do you have any setup guide for this? Maybe this all that is needed for dummies like me... 

Thanks in advance for your help! 

 

0 Kudos