Hello! So, maybe I am in the wrong place. I am looking for LTSC 2019 without the N. I was told not to use N edition back with LTSB 2016, as it contained limited licenses out of the box and such, ... I had difficult playing some files. Reason I am writing is: I installed LTSC 2019 and I am stuck at "Sign in with a Microsoft account" or join a domain. Is there no skip option? Thank you!
All 3 officially released LTSC ISOs contain non N. https://forums.mydigitallife.net/th...b-17763-xxx-pc-rs5.77945/page-51#post-1467631 "Join a domain" will be the option to be able to use a local account.
Joining the local domain worked! Thank you Enthousiast, you are the best I have the original 17763.1 from sep 2018, but am downloading the latest 17763.316 from feb 2019... besides cumulative updates, did anything else change in between those months? Since, I already have 17763.1 installed in virtual box, I am going to install Office 2019, and try activating those just to get comfortable with the tools and process
Only security updates between minor versions of LTSC/LTSB, that's the beauty of it, when you don't want feature updates that may break things and introduce bugs
Hi guys. Is there unnantend.xml with scripts optimised for W10 LTSC 1809 and W10 2004? Like this https://forums.mydigitallife.net/th...n-windows-10-1803-17134-1.77126/#post-1439403 Sorry maybe my questions stupid, but Im new in all this stuff, an embarrassment of riches
Updated the 1809 Updates Overview (17763.1339): https://forums.mydigitallife.net/th...-17763-xxx-pc-rs5.77945/page-216#post-1490183
So, even when I strip Windows 10 LTSC of all it's telemetry with group edits or some programs, could Windows 7 be still less invasive compared to it? Wherever I go, I seem to only find outdated information on that matter.
1. Telemetry is overhyped 2. Windows 7 is over and done 3. Chopping will only lead to (future) problems
Yo! I'm asking a simple confirmation. I've read a few pages back, I opt using LostED links from the first page. en_windows_10_enterprise_ltsc_2019_x64_dvd_5795bb03.iso. Do I still need to convert it?
I don't mind ALL telemetry, but from what information I could gather some of it seems very questionable. (Last thing I read was something published last year by the german BSI, and they inspected the LTSC version) Is there some source or thread I can dive into that will help me take a more relaxed stance? I don't mind them having some general hardware data, but their collecting seem to be exceeding that by far?
If you don't mind? as this question probably been answered before. What I understand is I'm opting the latest official release LTSC 17763.316. Does manually converting one provide a better ISO? from what I've read via manual method you can skip updates by already including it from your own generated ISO correct? Do both ISOs just end with the same build in the end?
By manual converting you probably mean to create an uptodate LTSC ISO? check the bottom of this post: https://forums.mydigitallife.net/th...b-17763-xxx-pc-rs5.77945/page-51#post-1467631
The ISO you downloaded is build 17763.316: https://forums.mydigitallife.net/th...prise-n-ltsc-2019.76325/page-164#post-1508318 The checksums you link at, are from build 17763.1
well the link where i downloaded the ISO didnt mention which build same for hashs post, i think links in this thread need to be updated. Anyways, the hash you linked it is matching the ISO, so its green light. Thank you
We will not believe what you are saying. This forum has the most accurate hashes, if one is looking tor such issues. A torrent can be uploaded by anyone, no way to make any verification. So, please check what you are talking here
He means the OP should be updated, but the owner of this thead, @Tito has not been online for a long time. This post should give all the possible info: https://forums.mydigitallife.net/th...b-17763-xxx-pc-rs5.77945/page-51#post-1467631
Ended up trying to install W10 on my brand new hardware, and was immediately greeted by a bluescreen without even installing Windows. Greeted me with a BSOD 0xc000000e. So I tried to install W7 instead. Also BSOD but with a different number 0x0000007E. My hardware seems to be fine, at least everything is being recognized in my BIOS. I'm now running memtest 86+ and will wait for its results. But I wanted to make sure: Could this be in any way related to my BIOS settings? I didn't make any changes to it, but it's my first MSI board and I'm fairly lost with their UI. I created my USB drives with the Microsoft DVD Tool.