No problems on my end, same goes with EAC. Like @farmers said, it's up to the developers to fix this. And from the looks of it, they have.
Yes absolutely down to BattlEye devs to fix, I was just wondering if anyone had tested. Sounds like you have so that's great!
I've only played some Rainbow Six: Siege though, so if you play Playerunknows battlegrounds (or other BattlEye games) i can't guarantee that it works.
this build is defo not ready for prime or RTM, my config is pretty straightforward, most if not all previos official versions upgrade-installed without issue, however I cannot afford to do clean install, too many customizations over the years, and this build fails @ safe_os boot phase, complaining about drivers or system restore points. I tried the known methods to circumvent this, i.e disable corsair link, intel RST, system restore. To no avail, so the OS rolled back and I am waiting this one out.
@er557: Which "customizations over the years" do you think may prevent a clean install of Build 19041.1 onto your system? It can only be hardware related ones. I installed this OS clean on several PCs and notebooks and didn't recognize any problem during and after the OS installation. By the way - what has a "Corsair link" or "Intel RST" to do with a fresh OS installation? The related storage drivers are either in-the-box or can be loaded.
you misunderstood, or maybe i didnt explain properly- I can't afford to do a clean install BECAUSE of all software installed and variuos items over the years, hence my usuall and only option is an in place upgrade-install of the new build, which i always done for official builds without issue. I am sure a clean install is compatible with my hardware, but i dont want that. So what i am trying to resolve is upgrade issues from 1909 v.535 to 19041. BTW, I have no dism or sfc issues, and mentioned the fixes as proposed elsewhere for corsair link and rst. One bug i did see eariler on was with build 1903, when unallocated drive space for over provisioning was rejected by the setup process until allocated. this is fixed now, but clearly not all scenarios are supported yet.
if u have a antivirus disable it what ever other software that is running in the background disable everything..if u change anything in the registry u mite need change it back to default.. then try to upgrade something their is interrupting the upgrade....i upgraded from the previous insider build with out any issues.
I DO have ADK, will remove it, but it is only a bundle of software, not drivers, why would it interfere, this is supposed to be supported. I might wait till official release and any blocking issues discovered, before I try once again and risk my system. I do have image backups of course.
I have the same issue with my AMD Ryzen+Vega based laptop. The same installer upgraded my Intel+nV based desktop without problems, so I suspected an AMD driver. Another difference is drive encryption (active on the notebook but not on the desktop).
@janos666 intel NV desktop here, so seems stumped at a dead end here, no encryption, with many 3rd party drivers installed, for instance creative, marvell, eset smart security. @jmtella will try without adk
I have been running 19041.1 since it's release on 10 Dec. 2019 as an Upgrade with Zero problems. EN_US 64bit
I do not know. But I had problems in several machines for having an old ADK. The only explanation is that at some point the installer uses the old DISM that is in the ADK. Clearing it the updates to 20H1 have gone smoothly on all my machines.
And another possible culprit "IP over USB" since this component of the previous versions of ADK fails to be installed on 19041. Spoiler