Your response doesn’t help. But I’ll bite.Sorry for the dig. I lost interest at Win 8. I run win 7 64 bit with inpunity. Has everything I need and (Fully controllable) and will not subject myself to Mr. Gates impulses. Once Win 7 64 bit proved to run processes in memory I knew I had to marry it. What more could I ask for? Device drivers: written and provided, control over processes and "call home"... doable. The tipping point was reached in my own needs and that's where I stopped.. Similarly for DJI Go 2.9.1.
Frankly if I could have stayed on WinXP I would have. Win 7 was then my go to OS for a long time. I never even went to Win 8 because it sucked. Microshaft even knows what a failure it was because they abandoned much of the changes and went back to something more usable in Win 10.
IIRC, I upgraded to Win 10 because I was suckered in by the last chance to update for free. I’m definitely not a knee jerk updater. I managed systems infra for a major investment bank for years and an important part was balancing between falling too far behind and being too much on the bleeding edge. Sometimes you get run into a cul de sac though if suddenly something you require doesn’t run on an old version of the OS so I decided to get the free Win 10 and be done with it.
Truth be told I have evolved into using it pretty much only for quicken. I do most everything else on my Mac desktop or iPhone. My Win 10 System is actually a virtual machine running on my Mac (using Parallels). And parallels throws another possible dependency in the mix for me. (I’m also not sure if my inability to install VLM is 32 bit related or VM related. My bet is 32 bit because I’ve not run into anything that knows it’s in a VM and won’t install.)
Now when it comes to drone firmware I believe version compatibility dependencies are fewer and that issue is less compelling as a driver to update. So I’ve downgraded my P4P to the beloved .509 version and there it will stay until a real compelling feature/fix is released and/or there is some dependency that crops up through, say, the SDK that ties a future version of Litchi to the AC firmware should that happen. I did the same with my P3S. Downgraded to a stable version and left it there.
I do have a physical machine with Win 10 that hasn’t been powered up in some time. I may fire it up and see if I have 64 bit version on there and if so, whether VLM will install. Right now, on the VM, the install program just throws an error that it’s not compatible with my system.