Not experiencing these random restarts on my second machine running version 1903. The only way to really find out for each case (maybe different from one user to another depending on hardware and software configuration) would be to have a system image backup and install it (upgrade). If not pleased or encounter those random restarts, system restore from the backup made before ought to come in handy.
maybe ill do that...but then again, I got Virtualbox installed, maybe doing a test with that should be able to prove/debunk the random 1903 restarts
I've installed 1903 on at least 30 different systems and 10 VMs, Nary a single random restart to be seen. I have not seen anyone posting in these forums about random restarts either.
It's very odd that from multiple sources I can read about massive amounts of breaking issues with 1903 and it's latest CUs, yet none of my systems has any issues what so ever.
UPDATE: Lol, just when I bragged about how well the system runs for me, I realized that my Logitech MX Master 2S connected using the Unifying receiver on my Lenovo ThinkPad A485 is extremely laggy and unreliable. I think this started with .295 update, because I have not noticed this issue before. The receiver works great on my other computer which does not yet have this update. Connection is very reliable over BT on my ThinkPad though.
After further examination, I realized connecting any Unifying receiver with any device (multiple different mice and keyboards) linked to my ThinkPad is a horrible experience. I need to report this to MS. Can't use the system like this.
Last edited by slicendice; 20 Aug 2019 at 06:01.
Ok, so last week CU kb4512508 tried to install, during re-boot phase got to 7% complete then re-booted and said unable to update...undoing changes.
That happened every time It tried to install.
Doing an in place upgrade using the latest ISO took me to 1903 build 18362.295....checked for updates, non available, great I thought, problem solved.
Today CU kb4512508 installed again only this time no re-boot needed and seemed to go without a hitch.
Still on 1903 build 18362.295.
I think we will get another CU again any day soon, seen loads of tweets from askwoody about vb script being broken and so far only the other win 10 versions being addressed but surely 1903 incoming soon. Not sure what ramifications that has for the normal user but I guess it’s going to have to be fixed judging from the noise. So we are prob going to have to do it all again
Last edited by Scottyboy99; 20 Aug 2019 at 11:10.
Installed the update manually using MSU file but the windows still wants to install the same update automatically.... Any reason for this to happen?
Quote