Just installed Windows 11 in Parallels, clicked on the Microsoft Store and got an error message (screenshot). The "reinstall" button did nothing. After the first reboot the store app ist completely gone. Already tried the following without any luck: - windows update - windows troubleshooter - uninstall / reinstall store via the terminal - switched from a local user to my microsoft account - activated windows license Anybody experiencing the same behavior after a fresh install?
Some additional infos: Sonoma 14.1.1 Windows 11 Pro, 23H2, 22631.2715 Parallels Version 19.1.1 (54734) MBP 14 M3 Pro I reinstalled win 11 via parallels multiple times now - with the same problem: no working store.
Exactly same behaviour for me here with Sonoma 14.1.2 - tried 3 times since yesterday, plus some magic command steps from other post found on the forum. So far no luck, so I would be adding my post here. I also submitted report ID 444173152
I am having the same issue. Have tried re-installing multiple times. Even went so far as to install via ISO and install parallel tools manually. What is going on? Why is the store broken? Has anyone tried installing windows 10 on Parallels 19?
Hm, don't think this is a Parallels-only problem. I reinstalled Win11 in UTM with an older iso-image and got the same problem. About a week ago the same iso-image in UTM worked ... perhaps MS stopped liking virtualized Windows installs?
Have same problem in Parallels 19. It is working in an earlier version of Windows that I installed 2 months ago. Having problems installing software (Barracuda VPN) when I get the store running.
Just to add. I have raised a ticket with Parallels regarding this problem. The technician was able to reproduce the behaviour on my system.
The issue "Can't install/update Microsoft Store on Windows 11 Pro (ARM)" has been resolved. Look in the thread.
I talked with Support engineer yesterday. He just reinstalled Windows and everything works fine now... I think the image that was used for installation was botched (it's beta dev channel ISO I think so it might have been caused by MSFT).