Discussion in 'Windows 10' started by Solarsails, Sep 15, 2019.
You need to login to view this posts content.
You need to login to view this posts content.
Enterprise 2019 LTSC = 1809 only
Thank you, sir. That at least clears up my dilemma a little bit; at least I know that I have to at least try out 1903 or one of those new fangled releases and hope that I can clean it up with MSMG good enough and if not then I have to stick with the "defected" 1809.
Any advice from some of you super-professionals would be very much appreciated? In your professional opinion which version should I use? I've been planning on using 1809 forever since LTSB... however... Apologies, I have been reading the forums, but now I'm pressed for time and even more stuck in a MOMENT of indecision. Everything I've read and know says stick with 1809... or is there an alternative route?
Your best bet is to do it yourself.
You worry about futile stuff, better be worried when you run into (expected) problems after chopping it
Ah! I am such an amateur. I have actually planed on testing, testing and more testing before a final implmentation. I mean it really doesn' take much to reinstal an operating system and I have a virtually unlimited supply of PC's not that they are necessary... You think that I should just leave it intact then and stick with 1809? I've been usign Win7ult for years and am finally switching to win10....1
Wyle E. Coyote... super genius; I like the ring to that... Wyle E. Coyote, super.... ... ...
At any rate think I'll take you up on that.
LTSC 1809 is the closest version of windows 10 (that's as up to date as possible) that you're going to get to windows 7 ultimate. The reason why is because it doesn't have microsoft store and lots of preinstalled b.s. that you don't need. You never needed the store with windows 7 and you don't need it for windows 10 either.
I'm not sure why you think 1809 is "defected" as I'm running LTSC 2019 (v1809) [build 17763.737] on my old HP machine myself and is running fine without the problems you are having. It took MS nearly several months to stabilize 1809 with either build 17763.316 (Feb. 2019 refresh) or 17763.379 (Mar. 2019 refresh)
Yes, that sounds exactly what I want to do. None of that un-required stuff clogging up the plumbing, so to speak. I've always tried to trim out what wasn't needed in Win 7, Win Xp and all the way down to DOS. Less stuff running and less stuff even in the registry is the best way, IMO. All of that store stuff and extra gunk running on the side just slws things down and opens the system up to security hazards... Help me understand what is the issue with 1903 and the others, is it just the store and bloat? What is undesirable in there.
All unfounded assumptions,...
You mean that store and add-ons have no affect on system resources or open your system to security problems? Gosh, of all the people who would say something like thatl... I've read a lot of your posts and quite a few of them seem to have had some good advice, but something like this is hardly debatable. I mean there are documented cased of store add-ons creating wide open security vulnerabilities. Surely this response was meant to address a different post? I mean these isues are hardly unfounded assumptions, they are proven to be factual.
Do you run store in your installs? Any other extra add-ons?
I don't use "virtual disks" at all, Solarsails. perhaps that's one reason why I have not experienced the problem...yet.
if MS will develop a "fix" for it, it won't be an "immediate" one (like with an upcoming CU that might be available near the end of September); could take several weeks or months for MS to fix the problem since it may not be a high priority for them
Try to copy some files under windows 10 and then right click the properties of the copied files directory to see if that issue surfaces for you. All the files seem to be there but the properties shows less files are there than were copied. Its a fairly diffuclt issue to language/explain when you try to discuss what is happening with oters... From my research it shows up in all manner of copying files, not just virtual disks. Its happened in just about every sort of copying functions.
perhaps you should post a youtube video about the problem so that I can believe you (because I'm not getting the problem - the properties of the copied files are correct on my end; so I'm not yet convinced that the problem occurs on all ltsc 2019 systems). that will be proof enough for me once you upload a video showing how the problem occurs on your computer
Have you rechecked if the (I mean ANY) absolute path length has really decreased below 256 characters?
Have you checked if conditions for a failure have really been met?
Suggested tool from that forum is TLPD ("too long path directory") ....
Hmm because of this problem and others related to file associations is that I did a downgrade to the W8.1 that works like a Swiss watch...