Windows Subsystem for Android / WSLg does not resize properly using FancyZones

[2001zhaozhao]

Microsoft PowerToys version

0.49.1

Running as admin

• Yes

Area(s) with issue?

FancyZones

Steps to reproduce

• Launch any app in Windows Subsystem for Android
• Try to snap the window to a zone

✔️ Expected Behavior

The window is resized to match the size of the zone.

❌ Actual Behavior

The window's top left corner is moved to match the zone, but the window does not resize, regardless of the initial window size or zone size.

Before snapping:

After snapping:

Other Software

Windows Subsystem for Android 1.8.32822.0

[crutkas]

Believe this may be same issue as #10942. Just wondering if the native window snap does it.

[2001zhaozhao]

Believe this may be same issue as #10942. Just wondering if the native window snap does it.

I think it is a different issue as the zones do appear in this case. The window simply does not resize properly. In #10942, the issue is that the zones do not appear at all.

[SeraphimaZykova]

@2001zhaozhao is it possible to resize this window manually to make it small enough to fit the zone? Some windows have a minimum size and FancyZones can't force them to be smaller.

[crutkas]

I need to verify wsa apps can be snapped

[towo]

FWIW, WSA apps can be snapped natively (on Win 11, obviously, stable channel) but do not snap to FancyZones as of 0.58.0.

[towo]

FYI this appears fixed for me w/ v0.59.1 and current Windows 11 stable.

[jaimecbernardo]

Thanks for the info!
@2001zhaozhao , does 0.59.1 fix it for you as well? /needinfo

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

[AdityaAgrawalRaipur]

issue still exists

[crutkas]

We are waiting for a fix from wsl team for this.

[crutkas]

/dup #10942

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!