Seems like we're being held hostage with Win 10 at least. I expect more so with 11. All new Native Instruments stuff requires 10 (NI locked up all their new stuff including libraries and instruments), Adobe will also screw you. Others only run their VSTs on it only.
I found this: https://atlasos.net/
Whole lightweight 64 bit version of Win (10 compatible). Needs powerful OpenGL GPU for programs that require it (graphics, video, photo and games. Other tweaking necessary.
Don't know about driver compatibility.
You have to wipe your boot drive to install and tweak MB settings. Heart and brain surgery.
It's worth a look but I'm not going to try it.
Windows 11
Re: Windows 11
"I’ve come to the conclusion that synths are like potatoes, they’re no good raw—you’ve got to cook ‘em, and I cooked these sounds for months before I got them to the point where they sounded musical to me." Lyle Mays
Re: Windows 11
Win11 can be installed on older PC's by using the IOT version of Win11 (preview 04/2024) Enterprise LTSC to bypass hardware requirements:
https://www.techspot.com/news/102707-ne ... orted.html
Here's a link to IOT Ent. LTSC on archive.org:
https://archive.org/details/26100-ltsc-x64-enus
-----------
Note with a TPM 1.2 chip on a Supermicro motherboard, i was able to install Win11 64bit and Xite Scope without issues, even though the CPU was reported as UNSUPPORTED and it asked for TPM2.0 in the requirements list. During install there was NO ISSUE--I did this last november on a USB stick built using MS's usb installer tool, and NOT via the IOT method above. Since IOT allows removal of components, I may eventually use this method to upgrade my WIn10 Scope PCI box to WIn11 via fresh install.
https://www.techspot.com/news/102707-ne ... orted.html
Here's a link to IOT Ent. LTSC on archive.org:
https://archive.org/details/26100-ltsc-x64-enus
-----------
Note with a TPM 1.2 chip on a Supermicro motherboard, i was able to install Win11 64bit and Xite Scope without issues, even though the CPU was reported as UNSUPPORTED and it asked for TPM2.0 in the requirements list. During install there was NO ISSUE--I did this last november on a USB stick built using MS's usb installer tool, and NOT via the IOT method above. Since IOT allows removal of components, I may eventually use this method to upgrade my WIn10 Scope PCI box to WIn11 via fresh install.
- Bud Weiser
- Posts: 2788
- Joined: Tue Sep 14, 2010 5:29 am
- Location: nowhere land
Re: Windows 11
Thx a lot !valis wrote: ↑Fri Apr 26, 2024 4:32 am Win11 can be installed on older PC's by using the IOT version of Win11 (preview 04/2024) Enterprise LTSC to bypass hardware requirements:
https://www.techspot.com/news/102707-ne ... orted.html
Here's a link to IOT Ent. LTSC on archive.org:
https://archive.org/details/26100-ltsc-x64-enus
I´m just dowloading the ISO,- just only to have it.
Questions,-
1.)
There´s a product key visable on the download page,- did you use that and IF, how many users might be able to use ?
Or did you use the/your product key from previously installed Win 7 Pro x64 or Win 10 (22H) Pro x64 ?
2.)
The usual Win10/ 11 language conversion (right click MS Windows icon to the left on taskbar > settings > language) worked w/o installation of a dedicated language pack ?
(I cannot find such lang-pack elswhere,- except for MS Office)
Since the downloadable ISO is english language, there should be no problem changing the langauge to german once the OS is installed and launched.
I have a Win 11 22H Pro x64 installed on my Lenovo W541 laptop showing similar "issues" when using "Why not Win11" application.valis wrote: ↑Fri Apr 26, 2024 4:32 am -----------
Note with a TPM 1.2 chip on a Supermicro motherboard, i was able to install Win11 64bit and Xite Scope without issues, even though the CPU was reported as UNSUPPORTED and it asked for TPM2.0 in the requirements list. During install there was NO ISSUE--I did this last november on a USB stick built using MS's usb installer tool, and NOT via the IOT method above. Since IOT allows removal of components, I may eventually use this method to upgrade my WIn10 Scope PCI box to WIn11 via fresh install.
TPM 1.2 inside "isn´t supported" as well the "processor", the "graphics" and one or two other "things" mentioned,- buit it runs smooth and receives MS Win 11 updates successfully.
And it´s a regular Win11 from Win10 upgrade and not "IOT Ent. LTSC".
Up to now, I refused to install SCOPE/XITE v7 on that laptop ´cause I hoped for the new ASIO and WAVE driver since a long time.
So,- does Scope (XITE) run well w/o any issues on Win 11 on your side ?
Did it need some tweaks and/or tricks to install and run flawlessly ?
According to the "IOT Ent. LTSC" version, I´d like to install on my rackmount DAW machine w/ RME Raydat as the audio/MIDI interface.
Currently it´s Win 7 Pro x64 still and I wonder which product key might work,- my Win 7 Pro x64 key or the one from "IOT Ent. LTSC" download page.
Every advise highly appreciated !
thx in advance,-
Bud
Re: Windows 11
I buy keys for typically $29 USD, I see them frequently advertised on tech sites and if you use them shortly after buying them they always work. Win11 Pro needs to be specified when purchasing (the keys are no longer interchangeable with Win10 as they were when Win11 launched). Here's an example on one such Ad.
I had zero issues with Win11 and Xite, I didn't do much tweaking for my Win10 Scope PCI box either. In fact the BIOS settings are stock on both, aside from one or two things that needed to be changed due to the type of motherboard (both have remote boot features that I turn off, remote SMC (System Management Controller) consoles and onboard GPU's that I don't use). The built in CPU IGP and graphics card are both left enabled, and I don't mess with core parking / EIST or etc. I did set PCI latency on both to 32 clk cycles on the PCI system, but no such thing is needed on the Xite box.
On all machines I run the current build of MS Powertoys, which allows me to toggle to keep the machine(s) awake and (optionally) screen on, and don't even find the need to change power profiles any longer. Note I don't run DAWs on either of these machines, though there are some things installed if I want to. I typically run Bidule and host some native plugins that I trigger from the remote DAW machine.
I had zero issues with Win11 and Xite, I didn't do much tweaking for my Win10 Scope PCI box either. In fact the BIOS settings are stock on both, aside from one or two things that needed to be changed due to the type of motherboard (both have remote boot features that I turn off, remote SMC (System Management Controller) consoles and onboard GPU's that I don't use). The built in CPU IGP and graphics card are both left enabled, and I don't mess with core parking / EIST or etc. I did set PCI latency on both to 32 clk cycles on the PCI system, but no such thing is needed on the Xite box.
On all machines I run the current build of MS Powertoys, which allows me to toggle to keep the machine(s) awake and (optionally) screen on, and don't even find the need to change power profiles any longer. Note I don't run DAWs on either of these machines, though there are some things installed if I want to. I typically run Bidule and host some native plugins that I trigger from the remote DAW machine.
- Bud Weiser
- Posts: 2788
- Joined: Tue Sep 14, 2010 5:29 am
- Location: nowhere land
Re: Windows 11
Thx a lot for your input !valis wrote: ↑Fri Apr 26, 2024 12:10 pm I buy keys for typically $29 USD, I see them frequently advertised on tech sites and if you use them shortly after buying them they always work. Win11 Pro needs to be specified when purchasing (the keys are no longer interchangeable with Win10 as they were when Win11 launched). Here's an example on one such Ad.
So,- you got the Win11 "IOT Ent. LTSC" version to run w/ such product key (see link above) ?
Here, I can buy a Win11 Pro 64Bit product key incl. bootable USB 3.0 stick for EUR 17,90,- but that´s not "IOT Ent. LTSC" Enterprise version(s).
Would the "IOT Ent. LTSC" version install and run w/ such key,- or do I have to buy a dedicated "IOT Ent. LTSC" version product key to do so ???
Thx for the PCI latency advise for PCI card systems !valis wrote: ↑Fri Apr 26, 2024 12:10 pm I had zero issues with Win11 and Xite, I didn't do much tweaking for my Win10 Scope PCI box either. In fact the BIOS settings are stock on both, aside from one or two things that needed to be changed due to the type of motherboard (both have remote boot features that I turn off, remote SMC (System Management Controller) consoles and onboard GPU's that I don't use). The built in CPU IGP and graphics card are both left enabled, and I don't mess with core parking / EIST or etc. I did set PCI latency on both to 32 clk cycles on the PCI system, but no such thing is needed on the Xite box.
On all machines I run the current build of MS Powertoys, which allows me to toggle to keep the machine(s) awake and (optionally) screen on, and don't even find the need to change power profiles any longer. Note I don't run DAWs on either of these machines, though there are some things installed if I want to. I typically run Bidule and host some native plugins that I trigger from the remote DAW machine.
I´ll run SCOPE/XITE from laptop which has Win11 Pro 64Bit already installed,- just because the machine works at it is.
I already tweaked w/ Win10 Privacy as I did w/ the other, a bit slower, laptop w/ Win10 22H installed.
The "IOT Ent. LTSC" Win11 version makes sense only for upgrading the Win7 Pro 64Bit machine.
That´s why I´m asking for which product key to use w/ the Enterprise Win11 version I downloaded yesterday using the link from your previous posts above.
So,- the most important question is:
When buying such $29 product key (or such I can buy here: https://www.softwarebilliger.de/betriebssysteme/windows-11-pro-usb/?c=601 ) for a more or less "standard" Win11 Pro 64Bit,- would that product key work for the "IOT Ent. LTSC" Win11 version too ?
It´s all about my currently Win7 64Bit rackmount DAW machine where it´s impossible to install a "standard" Win11 Pro 64Bit because of Microsoft hardware restrictions.
thx again,-
Bud
Re: Windows 11
The key is an installation key, and it should be retail. See the following links for an explanation of the differences between RTM Retail and KMS Client product keys, and between activation and installation keys (installation keys do not activate, but allow installation).
https://www.elevenforum.com/t/generic-p ... ions.3713/
https://winaero.com/windows-11-generic- ... -editions/
With Home and Pro, you can switch keys on the fly. Most of the components are already installed, but a few things will update via Windows update. I believe this is also possible with Enterprise LTSC, but--at least with Windows 10--you need to use the activation key as an interim step while not connected to the internet:
https://answers.microsoft.com/en-us/win ... 48435eb9fc (reply from DaveM121)
https://linustechtips.com/topic/1479546 ... ith-a-key/ (2nd post from TetraSky)
Once you have 'downgraded' via the key, you can then put in your retail acivation key ($29 purchase or whatever) and connect to the internet to activate. The iOT version's removal of key components should remain mostly intact, though a few things may still install via Windows update to ensure full Pro functionality.
https://www.elevenforum.com/t/generic-p ... ions.3713/
https://winaero.com/windows-11-generic- ... -editions/
With Home and Pro, you can switch keys on the fly. Most of the components are already installed, but a few things will update via Windows update. I believe this is also possible with Enterprise LTSC, but--at least with Windows 10--you need to use the activation key as an interim step while not connected to the internet:
https://answers.microsoft.com/en-us/win ... 48435eb9fc (reply from DaveM121)
https://linustechtips.com/topic/1479546 ... ith-a-key/ (2nd post from TetraSky)
Once you have 'downgraded' via the key, you can then put in your retail acivation key ($29 purchase or whatever) and connect to the internet to activate. The iOT version's removal of key components should remain mostly intact, though a few things may still install via Windows update to ensure full Pro functionality.
- Bud Weiser
- Posts: 2788
- Joined: Tue Sep 14, 2010 5:29 am
- Location: nowhere land
Re: Windows 11
Hi Valis !valis wrote: ↑Sat Apr 27, 2024 4:57 pm The key is an installation key, and it should be retail. See the following links for an explanation of the differences between RTM Retail and KMS Client product keys, and between activation and installation keys (installation keys do not activate, but allow installation).
...
Once you have 'downgraded' via the key, you can then put in your retail acivation key (...) and connect to the internet to activate. The iOT version's removal of key components should remain mostly intact, though a few things may still install via Windows update to ensure full Pro functionality.
Cannot thank you enough for all the info !
When my machine will run w/ this Win11 version and I don´t have to buy or build a new computer,- that will save a lot of cash !
thx and all the best,-
Bud
Re: Windows 11
Also note that this means that you can install with an installation key to test, you do not actually have to purchase a key to test if Win11 will install. Obviously, the easiest way to do this is by using a different drive, or imaging your current drive to make it back up before installing the new operating system system.
- Bud Weiser
- Posts: 2788
- Joined: Tue Sep 14, 2010 5:29 am
- Location: nowhere land
Re: Windows 11
Thank you,- perfect !
I´ll remove the Win7 Pro 64Bit system drive and put in another used 256GB SATA SSD for a test.
When it works, I´ll buy a new drive, clone and "downgrade"/activate when done.
Maybe I´ll create a dual boot,- Win7 and Win11.
B.t.w., w/ Win7 Pro 64Bit on that (AsRock) Z97 machine, I needed dedicated (Samsung and Patriot) NVME drivers for the 2 M.2 SSDs installed.
Do you have any clue if these will become obsolete w/ Win11 "IOT Ent. LTSC" and the follow up "downgrade" to Win11 Pro 64Bit ?
Bud
Re: Windows 11
Not sure which you mean obsolete, the drivers or the drives themselves?
The drivers were needed because the NVMe spec was created after Win7's initial gestation, and so the default Win7 installation doesn't support that protocol. I have not needed a driver for anything when installing Win10/11, and both of my Scope boxen are workstation boards with abnormal onboard components (SMC chipsets, unique bonded quad Network ports on one of them, a Supermicro specific thermal control chip, etc). I have...5? Win11 machines here now including an AMD 5950x/Asus with dual NVMe drives (and 3 SATA SSD's) and 2 small "NUC" style enclosures with NVMe drives as well (1 is an i5, the other is an N5105 low power chip).
The drivers were needed because the NVMe spec was created after Win7's initial gestation, and so the default Win7 installation doesn't support that protocol. I have not needed a driver for anything when installing Win10/11, and both of my Scope boxen are workstation boards with abnormal onboard components (SMC chipsets, unique bonded quad Network ports on one of them, a Supermicro specific thermal control chip, etc). I have...5? Win11 machines here now including an AMD 5950x/Asus with dual NVMe drives (and 3 SATA SSD's) and 2 small "NUC" style enclosures with NVMe drives as well (1 is an i5, the other is an N5105 low power chip).
- Bud Weiser
- Posts: 2788
- Joined: Tue Sep 14, 2010 5:29 am
- Location: nowhere land
Re: Windows 11
The NVMe drivers only,- not the drives.
Thank you,- that´s what I wanted to know.
I already had a more or less hard time finding the NVMe drivers for Win 7.
The easiest was Samsung,- Patriot not so much (there´s 1 NVMe PCIe 3.0 x2 drive for storage inside).
So I really hoped for embedded NVMe drivers in Win10 and 11.
all the best
Bud
Re: Windows 11
https://liliputing.com/microsoft-releas ... rivileges/Microsoft is bringing another Linux feature to Windows… although it’s an optional feature aimed at power users. Sudo for Windows is a command line tool that works a lot like its Linux counterpart, allowing users to run commands that require elevated permissions on a case-by-case basis.
In other words, you don’t need to right-click and choose “run as administrator” or open up a command prompt that has administrator privileges. You can open a normal command prompt or terminal windows and then type “sudo” at the start of any command that needs escalated privileges.