FerdinandO
Junior Member
In my setuperr.log file the monitor driver could not start too. Also the knownfolder CSIDL_PRINTHOOD could not be found.
Windows 10 Insider Preview 21382.1
- Thread starter CarlH2
- Start date
FerdinandO
Junior Member
This update was installed successful on my Asus novago with a snapdragon 835. So it is not an Arm64 issue in general.
Thats right. I think, it's only a problem for Apple M1
My setup:
Host: Mac Mini w/ 16GB RAM, 1TB SSD
Guest:
Processors: 4
Memory: 8192 MB (with Parallels try to always go with an exact multiple of 1024)
Adaptive Hypervisor
Shared Network
Disk Capacity: 256GB
I share as little as possible between the Mac and Windows: I share Mac folders and clipboard but no apps or Windows folders. I don't share the Mac desktop.
On my initial configuration I configured it for Software Development
Browsers can translate for you.
He said:
So I think that's parallel's problem as well. Because big advertising "with us windows runs on Apple M1" and then doesn't work correctly, I don't think it works!! As professionals, they should have known/imagined this
One other thing is that I activated Windows with a valid license from my MSDN subscription.
Ach so. Also kein Apple mit M1-Chip. Das erklärt das problemlose Update. Scheint ja auch nur ein Problem für Parallels auf Rechnern mit M1-Chip zu sein
Attachments
GiovanniM7
Junior Member
"So I think that's Parallels' problem too. Because advertise "we run Windows on Apple M1" and then it does not work correctly, in my opinion it does not work !! As professionals, they should have known / guessed it."
translate.google.com
Aha. Das ist ja ein Ding. Liegt das Problem denn wohl nur an der fehlenden Aktivierung? Ich kann Preview Windows 10 pro leider nicht aktivieren, da ich Lizenz nur für Version Home habe und eine Preview-Home-Version gibt es ja nicht. Mein Rechner ist ein MacBook Air 8 GB mit M1
The first thing I would check is your allocated memory. Set it to exactly 4096. Also, I would stop sharing any of your Mac folders. That gave me other issues.
Otherwise it might be activation.
Danke. Werde ich mal probieren. Aber wie ich aus den vielen Beiträgen ersehen kann, scheinen ja eine Menge Leute dasselbe Problem zu haben wie ich. Und ich denke, dass sich auch Parallels hierum kümmern sollte/muss.
Update: to test this situation further, I downloaded a new VHDX file from Microsoft (21354), created a new Windows10 instance and then tried updating it. It worked. Based on this, I infer:
A) Something low level in the old VM (like the BIOS) is a carryover from PD 16.3 and is interfering with the update and/OR
B) Coupled with a specific condition in 21376.1 OR
C) Some PD/VM hardware or sharing setting that got changed later.
A) Something low level in the old VM (like the BIOS) is a carryover from PD 16.3 and is interfering with the update and/OR
B) Coupled with a specific condition in 21376.1 OR
C) Some PD/VM hardware or sharing setting that got changed later.
PrzemyslawJ
Bit poster
Solved
I had the same problem but after disabling file sharing between mac and windows the installation went without problems after the whole file sharing operation can be enabled again
I had the same problem but after disabling file sharing between mac and windows the installation went without problems after the whole file sharing operation can be enabled again
Ich bin nach wie vor der Meinung, dass es die Aufgabe von Parallels ist, die Voraussetzungen für ein reibungsloses Funktionieren von Windows zu schaffen. Ich habe Parallels ohne Einschränkungen der Funktionalität erworben (ausschließlich für die Nutzung auf einem M1 Rechner)und es kann nicht sein, dass jeder für sich rumdoktern muss, um eine problemlose Windows-Version zu schaffen, zumal wahrscheinlich die wenigsten die Nerven und ggf. auch nicht das hierzu erforderliche Wissen (mich eingeschlossen) haben.
triplespeed
Bit poster
Worked for me by setting VM memory to 4,096 (was 3GB) and stopped sharing Mac folders as suggested by ErikR4
I will say I am using my same VM from January. What I am thinking is that an unactivated Windows is good for 180 days. My guess is that by downloading the vxhd to an unauthorized system (Parallels) you are not getting the benefit of a hardware license. By downloading a new VXHD you got another 180 days. I think I might have a backup of my unactivated vm somewhere. I can try to update it and see what happens.
Maybe try something like this:
How to Extend Windows 7/8/8.1/10 Trial Period for One Year (techperiod.com)
So, my backup that hadn't been activated upgraded just fine so I don't think activation is playing a role.
My x86 VM was showing the same expired error but it upgraded just fine.