Okay, this is going to be a long one 🙂
The problem is that the 19041 version we are running is the one everyone is going to be running within a few months, since it is the final version of 20H1.
Going to a preview of 20H2 is not going to help - instead, what Autodesk should do is start working on getting Fusion 360 fixed, so people can use it once it is released to the general public.
If not, you are going to end up in the situation where your software will prevent people from upgrading - and telling "normal" people: "Sorry, you have to install a preview build of the next version of Windows to be able to use our software..." is not going to be good idea.
I do know something has changed in the 20H2 builds currently available that make is possible to use Fusion 360, but that is not the point I'm trying to make - I'm trying to make you aware that within a relative short timespan, normal, non-insider people, are going to be using the 19041 build, which your software currently isn't working with - and if you don't, you will end up with alot of angry users and most likely some negative press, since you have been aware of it.
What you should do is jump on to the final build for 20H1 as soon as it is released (mid december 2019) and start testing and fixing problems with your software, so when 20H1 is released to the general public, you already have ironed out your issues, instead of just waiting and telling people who are early adopters of it, that they have to go to 20H2 builds to be able to use your software.
I'm not trying to be unreasonable and demand that it is fixed right away - instead, I'm trying to convince you to go for "Okay, we'll see if we can fix it, so people will be able to use it on day 1 of it's general release" instead of "To be able to use it, please install a preview build from the 20H2 insider preview... oh, you want the stable release from Microsoft? Sorry, we just got it the same day as you - please allow us a few weeks to come up with a fix".
Having early access to the final version of the operating system should be taken advantage of by you are a software development company, so you are ahead on new releases.
Most likely that is already the case (if not, you need to take a look at your development workflow) - so the easy thing to do would be to just let people know you are working on a fix, instead of pointing people to the 20H2 branch, which is not an option for most people this early in it's release cycle.
Please don't take this as an attack, I'm trying my best to help guide you (Autodesk) on what should be done to avoid a lot of trouble in a few months - I don't mind the wait, my main machine is still on the 19H2 build, since I'm only using 20H1 for testing the software I need, to make sure it works, and help testing and fixing issues where needed.
Best regards, a fellow software developer 🙂
Fusion
