Windows 10 Insider Preview 21382.1

C

CarlH2

Junior Member
The new insider build gets to 20% and then you get the error:
Windows 10 Insider Preview 21382.1 (co_release) - Error 0xc1900101
On Reading up online Error 0xc1900101 usually indicates a hardware issue.
Will this require a new Parallels update to continue?
As Windows is reporting the current version as end of service.
 
wahrscheinlich gleiches Problem, Download von Preview 21382.1 steht noch aus, aber es steht unter Updates verfügbar - "Ihre Version von Windows(z.Z. Preview 21376) hat ihr Dienstende erreicht!!! Da ich ja nun auch Parallels extra für meinen Apple Air M1 gekauft habe, hoffe ich, dass da schnell eine Lösung gefunden wird und zwar für alle, denn ich habe nur eine Lizenz für Home und konnte bislang die Pro-Version auch gar nicht aktivieren:(.
 
I too face the same problem. I am sitting for hours trying to resolve but, in vain.
Windows 10 Insider Preview 21382.1 (co_release) - Error 0xc1900101
 
same problem here

interesting to note that it also is a struggle to download the fully install BITS as well - maybe MS are having somer service issues
 
In contrary to running Windows 10 on Intel processors, Microsoft is NOT supporting Windows 10 on ARM running on Apple M1.
I got the following reply from Microsoft's Marc Sweetgall:
>>
Hey Ferdinand,
Thanks for reaching out to report an issue and for continuing to use that Asus NovaGo!
However, please note that Windows running in a VM on Apple M1 is not a supported or tested configuration. We only support Windows on ARM VMs running on Windows 10 ARM-based PCs with Microsoft SQ1, Microsoft SQ2, Qualcomm Snapdragon 8cx, or Qualcomm Snapdragon 850 processors as listed at https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewARM64.

Thanks
Marc
>>
My complaint was that the single stepping exception used by Debuggers such a WinDbg or VS2019 Remote Debugger, crashes Windows 10 on ARM with a KMODE_EXCEPTION_NOT_HANDLED.
Subtle hardware differences between Apple M1 and other ARM processors could be used by Microsoft to make it impossible for us to run Windows 10 on ARM in the near future...
 
kundanno said:
in all fairness to Parallels, this is not their problem per se. This is a Windows issue that happens every so often. And then it goes away. It is a Microsoft problem.
Click to expand...
Also ich denke schon, dass das auch Parallels Problem ist. Denn groß Werbung machen „bei uns läuft Windows auf Apple M1" und dann funktioniert nicht korrekt, geht meines Erachtens nicht!! Als Profis hätten die das wissen/erahnen müssen.
 
Harry12 said:
Also ich denke schon, dass das auch Parallels Problem ist. Denn groß Werbung machen „bei uns läuft Windows auf Apple M1" und dann funktioniert nicht korrekt, geht meines Erachtens nicht!! Als Profis hätten die das wissen/erahnen müssen.
Click to expand...
I wish I could understand German.
 
BTW, I used Google translate to decipher what Harry 12 was saying. Using the windows update diag utility, I determined the error to be "FindAbruptDownlevelFailure" - and upon digging it appears that Windows tries to update BIOS or low level drivers and fails. As an aside, I was able to get my x86 VM (running on VMware Fusion) to 21382.1 no issues. Here is the error for your consideration.

Matching Profile found: FindAbruptDownlevelFailure - 55882B1A-DA3E-408A-9076-23B22A0472BD
SetupDiag version: 1.0.0.0
System Information:
Machine Name = <removed>
Manufacturer = Parallels
Model = Parallels ARM Virtual Machine
HostOSArchitecture = 1033
FirmwareType = UEFI
BiosReleaseDate = Unknown
BiosVendor = 16.5.0 (50692)
BiosVersion = 16.5.0 (50692)
HostOSVersion =
HostOSBuildString = 21376.1.arm64fre.co_release.210503-1432
TargetOSBuildString = 10.0.21382.1 (co_release.210511-1416)
HostOSLanguageId =
HostOSEdition = Professional
RegisteredAV = Windows Defender
FilterDrivers =
UpgradeStartTime = 5/16/2021 8:43:57 AM
UpgradeEndTime = 5/16/2021 8:45:41 AM
UpgradeElapsedTime = 00:01:44
CV = +6UNTTPT+E64eqXw
ReportId = 7559FC2E-E283-4AAE-AD50-E5C131864586

Error: SetupDiag reports abrupt down-level failure.
Last Operation: Finalize
Error: 0xC1900101 - 0x50010
LogEntry: 2021-05-16 08:45:23, Error MOUPG CDlpActionImageDeploy::ExecuteRoutine(537): Result = 0xC1900101[gle=0x8007000d]
Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.

Last Setup Phase:
Phase Name: Downlevel
Phase Started: 5/16/2021 8:45:23 AM
Phase Ended: 1/1/0001 12:00:00 AM
Phase Time Delta: 00:00:00
Completed Successfully? False


Last Setup Operation:
Operation Name: Start Monitoring Driver
Operation Started: 5/16/2021 8:45:23 AM
Operation Ended: 1/1/0001 12:00:00 AM
Operation Time Delta: 0:00:00:00.0000000
Completed Successfully? False
 
You must log in or register to reply here.
Back
Top