The only thing I have to say is make sure you stop all updates occurring....there seem to be never ending automated ones happening every time the sky is clear and they occur when your back is turned in the middle of imaging runs.
You can make the auto updates a lot less intrusive. Windows 10 auto restarts happen outside "active" hours and you can change the active hours manually to any 18 out of 24 hour window you like.
On my imaging PC I have the active hours set to 8PM though to 10AM and have never had a restart interrupt a session.
You can make the auto updates a lot less intrusive. Windows 10 auto restarts happen outside "active" hours and you can change the active hours manually to any 18 out of 24 hour window you like.
On my imaging PC I have the active hours set to 8PM though to 10AM and have never had a restart interrupt a session.
I can’t recall the exact process (google will tell you) but I made a change in the back end that resulted in no updates at anytime (even the download) unless I tell it too - nothing automated at all
You can make the auto updates a lot less intrusive. Windows 10 auto restarts happen outside "active" hours and you can change the active hours manually to any 18 out of 24 hour window you like.
On my imaging PC I have the active hours set to 8PM though to 10AM and have never had a restart interrupt a session.
And, starting from W10 1903, you can postpone updates to several weeks, even with the home edition.
The difference being that further W10 versions are likely to be released for some time yet and support by that document (For each version) will be 30 months after release of that version.
W7 however is dead in the water and is only occasionally getting a patch released when some suitably horrible security flaw is uncovered.
The difference being that further W10 versions are likely to be released for some time yet and support by that document (For each version) will be 30 months after release of that version.
<snip>
I’ve been running Windows 10 for 3 years now on my dedicated Astrophotography laptop (it controls my mount - tracking and Goto , assists with PA , image acquisition and capture and image stacking and post processing) and it’s worked flawlessly. It never gets connected to the internet !!! ( except for maybe once a year for new software or new software versions )
Completed Images are transferred via USB stick to my desktop
Basically a standalone computer !
Just click on "Don't remind me again" and that should be that.
I no longer see what the issue is with W10 aside from cost if you don't already have it. I have been using it for years including on my imaging PC and I have no more issues with it than I had with W7.
To be honest, if you can confirm our gear all has drivers for 10 you can still "Upgrade" from W7 for free if the software cost is the issue. They no longer push the free upgrade line but even recently I installed it on an old W7 machine and the servers take the W7 product key and activate W10 with it. I presume you can only do it once per W7 key rather than being able to activate new hardware every three months or so which was how W7 allowed for hardware upgrades over time, but I have never tested that.
Is there any reason that your acquisition computer needs to connect to the internet?
I have an old win10 lappy in my observatory (my wife's retired computer ) for the camera and a win7 similar one used for telescope control. Neither connects to the internet and I have put them on airplane mode so they don't try to connect to anything. I transfer my images to my home computer using a flash drive.
All the drivers work well and I don't see how any upgrade will make a working system better.
Only change to win 10 if there is a risk and you can eliminate the risk if the computers are stand alone.
Ages back, wasn't there a ' concern ' that Win10 had a lot of ' background ' processes ' snooping ' on the user....obvious while the Computer was on Internet.
Also, Updates couldn't be turned off...!!
That's why I stayed away from it......or is there a way around it...eg: Go into the Registry and start ' hacking ' things.... changing things from ' True to False ' or plain disabling processes.
Going into the Registry, one needs to know exactly what there doing, or all sorts off problems happen.