It's a toy. People should treat it as a toy. Always have a backup Windows DVD or USB to install a stable OS with. Anyone who installs a leak as their main OS and then complains about data loss is foolish.
WinNTSetup is custom software that may or may not use the official winpe dism api. I already solved this problem with my diskpart setup script and @Enthousiast made a script installer in that he has graciously put in the LEAK thread. All you gotta do is put the iso in one folder and run the script. Rufus the result iso onto a USB, boot it, shift-f10 and type "menu" to run the diskpart setup script that bypasses the tpm 2.0 check and formats the target drive for you. We've already done the work.
Honestly, I feel you. It's a new toy, but I'll probably stick with LTSB/LTSC after I play with it. I don't like bloat in my OS. Even LTSC has too much bloat for my liking. I'd LITE it but I want it to be as stable as possible and not second guess my own work. I kinda wish MS sold a bare minimum business version. I'd use the hell out of that.
Quick question: Since Windows 11 is from the co_release branch.. And all recent dev channel builds come from co_release, is it correct to assume build 21390 is an (early) build of Windows 11?
It could be a default font association. I recently played a video game where the font was all messed up because it was too large because the default association was set to Segoe or something and changing it to Gothic made it much more thin and appropriate for the game. I should warn you that when you find the registry keys that are associated with those associations, you should screenshot the page and never lose it because a lot of programs use those default fonts and you will change more than you can possibly imagine. I'm sorry I don't remember them off the top of my head but search the web for changing windows default font associations and you will find it pretty easily.
Yes, but Microsoft stripped W11 improvements from 213xx to keep them secret until next week. Only minor teasers (icons, etc) are presents. Insider Dev is also stopped and they only feed the channel wirh "empty cumulative updates" for 21390 build.
After a couple days of using Windows 11 exclusively, I've found a few things that don't work on my end: 1. The taskbar transparency is wonky, either have an opaque taskbar or have everything practically float. 2. Windows Hello only works on setup and the first restart, it ceases to work after that and checking the sign-in options in settings makes the app lock up. 3. Can't install .NET 3.5, it always returns an error. Not sure if these are because of my hardware or the buggy software but these are the only issues I've found in the build.
install .NET 3.5 21996.1.210529-1541.co_release_CLIENT_CONSUMER_x64FRE_en-us.iso\sources\sxs\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab 1. Mount iso with explorer. e.g. D drive 2. Run CMD as Administrator 3. Run the command to install Code: dism /online /add-package:D:\sources\sxs\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab Or copy microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab to C drive, then run Code: dism /online /add-package:C:\ PS. 1. Make sure that there is only .NET35 package in C drive, otherwise it will install all available cab files in C drive. 2. Some cab file can not be successfully installed. Under such circumstances, extract the cab, and install by the extracted folder. e.g. 123456789.cab 1. Extract 123456789.cab to 123456789 folder 2. Run the command to install Code: dism /online /add-package:C:\123456789 PS. Make sure that there are both update.mum and update.cat in the extracted folder. Some cab or esd package does not include .cat. Then it will fail to install such a package. Under such circumstances, Way1: Copy its package .cat and rename it as update.cat. e.g. 1. Copy Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~10.0.21996.1.cat 2. Rename the copied .cat as update.cat Way2: install such a package directly with its package .mum. Code: dism /online /add-package:C:\123456789\Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~10.0.21996.1.mum Remember: .mum and .cat are a couple for each and every package.
Its still very confusing to understand whether Microsoft will release a windows 11 Enterprise LTSC version or not, since win10 LTSC has support till 2025. Or else will there be LTSC 2022 only based on windows 10?
Well I would assume they will announce any such plans at the same time they announce other business licensing versions. They'll probably do it shortly after the initial Win11 announcement.
I don't think 21390 belongs to Windows 11, as there's a build number jump from 21390 to 21990. So 21990 is where I consider the start of Windows 11.
Fear mongering, he shows no evidence. We would've seen dozens here complaining already. Including myself. Also, the news reporters who used their damn Windows account on the leaked build. Bulls**t. BTW, the excessive emoji usage makes me feel like a boomer wrote that s**t.