It appears that "ATLAS" (22H2) is simply a set of MOD Scripts to remove all the garbage from an install done with a OEM ISO image. In essence OEM Windows bits should be able to be installed via optical disk, usb, or any other medium of transport. Just get yourself an OEM ISO image from where ever, run the OEM install, get it booted up, and then set the scripts loose after the OEM install is completed.

This thing takes out a LOT of functionality including printing, and more vital networking which I need for my backend lan. The LAN stuff could be re-enabled fairly easily had they NOT disabled Powershell which makes any reversal of the settings impossible. Not for me I'm afraid. I give this package two thumbs down since they do not seem to provide a viable method for restoring the vital services needed to be productive. Decidedly it doesn't (or can't) remove ALL the telemetry present without doing some pretty deep cutting and re-engineering. I have been able to reverse much of the OEM garbage myself, keep the thing OFF the internet and away from ms update and still maintain vital backend lan communications with the other machines on my domain, printing, and keeping within the lines of ALL my media production stuff working OK.

The atlas OS cats don't seem to keep archives around for folks that would like to use lesser versions than just the latest 22h2. The "playbooks" are not backward compatible with earlier builds and will simply beg out if you attempt to run, say, the 22H2 playbook on a 20H2 build for example. They also seem to advocate for downloading "updates" for windows. The script run will not complete without it requiring a internet connection to download "updates". This I find rather comical coming from a lot who have taken great strides to deliver a "crap-free" windows install. Since every "patch tuesday" windows update will attempt to REVERSE everything they have done to date.

 

Last edited: May 1, 2023

Well i have run my win 7 pro that i installed on a computer i built over 10 years ago and it has been rock solid

 

And what is "stable" then? MacOS? Linux? As I have said before - I see just as many apple peeps as windows peeps in here having all sorts of issues. Many of them self inflicted. The OEM distributed versions of WINDOWS or MacOS are all basically dog meat until an end user actually does the job of "optimizing" them for safe and sane functionality doing whatever application is needed. Linux, as far as I'm concerned is off the radar when it comes to the stuff of serious media production.

on a side note -

Windows LTSC is a Corporate ENTERPRISE version of windows designed for doing site/corporate wide domain roles like PDC, BDC, FSMO, CERT Servers, etc, and special single purpose applications within a corporate networked environment. Mainly for machines that require very little maintenance with relatively static code bases that never (or hardly ever) change.

"The Long-Term Servicing Channel is not intended for deployment on most or all the PCs in an organization. The LTSC edition of Windows 10 provides customers with access to a deployment option for their special-purpose devices and environments."

The ENT LTSC versions of windows in some cases do not even contain code for processing audio or video depending on the task for which it was deigned... NOT a tool for media production...

 

Last edited: Apr 30, 2023

That's why I kept the previous (downloadable iso) release, and yep, playbooks don't work on a previous build.

 

I was going to ask if anyone has a copy to share. Any chance you can share yours or is it specific to your computer parts?

It would be nice to have a setup disk on the sister site that covers a basic music setup.

 

The only Windows 10 version that comes without heavy DPC latency is v1809.
With v1903 and up DPC are a nightmare to handle.

 

Do you know what the DPC Latency does in relation to our DAWs?

I noticed that using a lot of Arturia locks the computer so I stopped using those and it seems like it locks when I open a plugin using a lot of graphics. I have dual monitors which probably doesn't help but the graphics card is a gaming card so its powerful enough to handle anything the DAW can throw at it... So that leans towards something like DPC Latency causing issues... I started saving my Stems as ALS before freezing and that sorts out my lockups.

 

nahh I had Windows 1909 for a long time and it had no DPC latency issues. If I remember correctly 1903 had some DPC latency issues that got fixed with an update:

Now I'm using the latest Windows 10 version (22H2 build 19045) without any problems. Only "problem" is that you should be carful using Ultimate Performance in Power Plan since it can create latency spikes (at least on my system). No problem since my system function good on High Performance:

System on High Perfomance:

 

Last edited: May 1, 2023