Windows 1903 - just reverted back to 1809

[GoldenX]

Something seriously wrong with MS and their stupid update.

I was prompted to update to the latest version of Windows 10. I choose "pick a date" and never saw any prompt to actually pick a date. I didn't think anything else of it. I come back to my server a short while later and I can't remote into it, so I connect it to my TV and I see it's on a do not restart Windows is updating screen....WTF? So I wait....the do not restart screen goes away and my system goes to a black screen and powers off. It never restarted like it should based on past experiences with these updates. I waited for a good while before I bothered turning the system back on - it comes back up and.....goes immediately windows repair screen.

Repair doesn't work.
System Restore doesn't work - no restore points found
I check the drive via command prompt - my 4TB drive is empty! Oh joy!

To make things worse, I was in the middle of doing a backup on a new HDD (dog knocked the tower hard when going on one of her apeshit "I have to run really fast and nothing will stop me" modes, she leapt the side of the couch and into the small area in the corner that the tower sits on a small table. The system wouldn't boot into windows. I swapped drives and the system loaded up. One drive won't spin, but no worries, the backup worked so I got a replacement and it came in the other day) when Windows decided it would update and restart my system even though I choose to not update. So, now my new HDD has nothing on it still and my main HDD appears to be an empty shell.

I'm sitting through the grueling process of EaseUS Data Recovery to see if it can pull up all the data on my main HDD for my plex server. So far it's found 450GB out of around 2.25TB that I had with the scan process over the past 30 minutes (only around 10 hours left) - thousands of hours of movies/TV shows/pictures.......I hope I can recover all the videos, I don't want to spend hundreds of hours ripping my DVDs and Blu-Rays again.

I have horrible luck when it comes to Windows 10 updating on my plex server. This is why I haven't put Windows 10 on my gaming rig.

If it's a server for streaming, just put Linux on it with samba shares. Save yourself the headache.

 

[neatfeatguy]

If it's a server for streaming, just put Linux on it with samba shares. Save yourself the headache.

I do use it as a second gaming system - one that the kids can utilize for their games or if my brother comes around to visit, we can co-op games without him needing to drag his computer over. Though, I am tempted to just say screw it to Windows for the server and try out Linux with the luck I'm having.

Right now my data recovery scan is sitting at 1525GB. Looks like things are going in my favor so far.

 

[Mescalamba]

1809 is the latest one, with 17763.316 being the latest ISO.

[DISCUSSION] Windows 10 Enterprise (N) LTSC 2019

Official MDL Thread on Build 17763 https://forums.mydigitallife.net/threads/77945/ Download + Hash...

forums.mydigitallife.net

Hm, might "update" then. Thanks for info.

 

[biffzinker]

like taskbar color is stupidly flat grey and there is nothing i could do to make it black...

You realize there is a new light theme in the 1903 update? If you want your taskbar black all you have to do is switch back to the original theme in settings.

I have heard from several folks that the old Classic Shell no longer works as of 1903. Or at least for now. They haven't tried Open Shell yet as I've suggested

Open shell is working for me going on a couple of weeks now after the upgrade.

 

[SL2]

When the 95% market share OS fails constantly after each updated version, we get the right to complain.

Of course, I'm one of those as well sometimes. However, to me there's a limit for how much complaint you can read, and after that it just gets tedious. I'm talking specifically about Windows issues here.
In one corner we've got NBR forums, with each post containing 'microsoft' spelled in various ways, as if we haven't seen that enough of that through the decades.
Then there's mydigitallife forums, where all the negative comments gets drowned out by the sheer amount of knowledge and patience.

I guess I've read too many of the former kind when I replied to the OP, my bad.

 

[Valantar]

It's weird how there's so much talk of issues with this, yet I've never seen a single W10 update issue across the 5 W10 machines in my household. Or, scratch that, 4 - my work laptop is managed by my employer and still on 1803. Still, I tend to update relatively early, and I've never seen significant bugs. And that's across a 1st-gen Biostar Ryzen motherboard (if anything caused weird driver errors, it ought to be this crappy motherboard!), a Threadripper system, and old FM2+ APU system and an Intel-based XPS 13.

Havent tried this yet, but I'll likely push the upgrade on my main desktop in the next week or two. Don't see any reason not to.

 

[FYFI13]

It does, get LTSC or Server.

No no no no no, not even close. I can remove UWP apps and some other stuff myself. I'm talking about truly lightweight OS.

 

[lexluthermiester]

I think Service packs worked better more often than not, even though you won't get anything new for a while.

This! All day long this!

They haven't tried Open Shell yet as I've suggested

Works fine.

I was prompted to update to the latest version of Windows 10. I choose "pick a date" and never saw any prompt to actually pick a date.

Go into your Services editor in the Computer Management console and disable both "Background Intelligent Transfer"(which Windows update depends on) and "Windows Update". You will then not have to worry about it.

 

[bonehead123]

I have heard from several folks that the old Classic Shell no longer works as of 1903. Or at least for now.

I can confirm this too, but everytime I boot from the partition that has CS installed, I get a pop-up that says "Classic Shell needs to reconfigure itself for the new OS". I click OK, then a red error pops up with some exception technobabble, I click OK again and it launches and functions normally thereafter...

Not sure whats up with that, but thats not my primary boot partition anyways, so I may research it further when I have some free time....

 

[lexluthermiester]

Not sure whats up with that, but thats not my primary boot partition anyways, so I may research it further when I have some free time....

No need, just use Open Shell. It's the replacement for Classic Shell based on the same source code which was released by the dev.

 

[Vario]

Still on 7 no problemo

 

[bonehead123]

No need, just use Open Shell. It's the replacement for Classic Shell based on the same source code which was released by the dev.

Thx Lex, will check it out tomorrow pm

 

[MrGenius]

1. My custom lock screen pic is blurred...WTF?

2. Installing AMD graphics drivers causes my entire screen to change to a solid color(so far either red or magenta) until I restart.

3. They changed the location of icon files. I had to figure out where they went(C:\Windows\SystemResources\imageres.dll.mun), so I could do my "make the blue and yellow UAC shields disappear" trick. Thankfully I was able to perform that without issues.

Other than that...oh wait...one more...

4. I can't stand the way they changed the Downloads folder to show separate groups. Hopefully there's an easy fix for that. If there is, and you know of it, I'm all ears.

Other than that...it's fine.

 

[Naito]

4. I can't stand the way they changed the Downloads folder to show separate groups. Hopefully there's an easy fix for that. If there is, and you know of it, I'm all ears.

Go to the View tab, click the Group by menu, select None

 

[biffzinker]

My custom lock screen pic is blurred...WTF?

Transition animation starting with 1903.

 

[Chomiq]

1. My custom lock screen pic is blurred...WTF?

Only when the sign-in screen is activated.

 

[birdie]

The last stable OS from Microsoft was Windows 8.

The last not completely sucking in terms of UI was Windows 7 (too bad it won't be supported starting January, 2020).

Windows 10 has been a total disaster.

At the very least we have LTSC which I happily use. Rock solid and doesn't get reinstalled each six months. And of course I have OpenShell installed, Cortana/OneDrive disabled, Telemetry reduced to security.

Kids may "enjoy" the latest and greatest and have wonderful bugs all around.

 

[Naito]

I must have a different build to most, as I rarely experience bugs since the first milestone update years back...

 

[FYFI13]

I must have a different build to most, as I rarely experience bugs since the first milestone update years back...

Same OS build works differently on different hardware configs and environments.

 

[Chomiq]

I must have a different build to most, as I rarely experience bugs since the first milestone update years back...

So did I, until I've installed 1903 two days ago to give it a try. Yesterday Firefox entire display engine started to break down up to a point when the browser basically CTD'd with a black screen. I've never seen that happen on my PC. Today I had to major slowdowns of entire system without any logical reason behind it, audio playback slowed to a crawl, cursor became unresponsive like it was running at 2 fps. Reverted to 1809 few minutes ago. Shame on me for giving MS a chance.
On top of that they've removed the Semi-Annual Channel from the WU, so now everyone is stuck on the same crippled update ring.

 

[rtwjunkie]

On top of that they've removed the Semi-Annual Channel from the WU, so now everyone is stuck on the same crippled update ring.

Oh wow. The news gets worse and worse. Every day I take a look at a spare copy of W8.1 that I leave on the desk of my main rig. It consoles me to know that even without mainstream support, it at least is stable every day and every update. One of these updates, I may just stop looking at it and use it.

 

[Naito]

Same OS build works differently on different hardware configs and environments.

I either run or maintain 9 machines of various gens, not including dev machines at work, and still haven't had issues with build 1903. In the very early days of 10, I did experience a few BSODs, however

 

[Valantar]

I either run or maintain 9 machines of various gens, not including dev machines at work, and still haven't had issues with build 1903. In the very early days of 10, I did experience a few BSODs, however

As with most cases I suspect this to be a "people with issues are disproportionally loud" type of situation. Yes, some updates have had significant issues, but this does not look to be one of them.

For my part, I could never go back to an earlier Windows version. I liked 7, but want too many of W10's features. Heck, the task manager alone is worth the upgrade IMO. And W8 and W8.1 were a hot mess.

 

[Chomiq]

As with most cases I suspect this to be a "people with issues are disproportionally loud" type of situation. Yes, some updates have had significant issues, but this does not look to be one of them.

For my part, I could never go back to an earlier Windows version. I liked 7, but want too many of W10's features. Heck, the task manager alone is worth the upgrade IMO. And W8 and W8.1 were a hot mess.

8.1 was perfectly fine for me, ever had any issues with it. That's why I refused to update to W10 up until late point when they've started to disable the "disability" free upgrade path.

 

[r.h.p]

He's inquiring to what the error was, not what a BSOD is, if you re-read FordGT's post. There's usually an EventID in system logs and a 0x00000xx code, sys or dll, etc. related to the BSOD bugcheck entry that can help diagnose the issue and resolve a resolution.

didnt have that just normal upgrade via the tpu non-media creation tool