|
|
Post by MartinT on May 25, 2019 11:44:36 GMT
Windows 10 1903 update installed perfectly fine on most of our machines at work and my own machine.
However, we found 11 machines that had been upgraded from W7 to W10 barfed over this update and left the machines in a recovery state.
So, if you installed vanilla W10, there seems to be no issue. If you upgraded from W7, proceed carefully and make a backup at the very least. Even better, make a vanilla install of W10 as it's very stable like that.
|
|
|
|
Post by Slinger on May 25, 2019 12:07:37 GMT
Strong and stable, Martin?  |
|
|
|
Post by MartinT on May 25, 2019 12:52:36 GMT
Both my home Gigabyte BRIX and my work Surface Pro are great work tools and ultra reliable. Don't know about strong, though  |
|
|
|
Post by Slinger on May 25, 2019 13:31:54 GMT
I'm currently installing " 2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934)" Which it's offered me within the last couple of hours and is now 74% done. I may, or may not, be back shortly. |
|
|
|
Post by petea on May 25, 2019 13:33:00 GMT
You could probably carry two cups of tea and maybe a small plate of biscuits on one, but a decent sized coffee and walnut cake as well would probably be a bit too much for one I would guess! |
|
|
|
Post by MartinT on May 25, 2019 14:34:21 GMT
|
|
|
|
Post by Slinger on May 25, 2019 15:05:07 GMT
Like I'm going to trust Windoze if I'd just forced it to do something it hadn't intended to do.  |
|
|
|
Post by MartinT on May 25, 2019 15:19:32 GMT
You'd rather it creep up on you? |
|
|
|
Post by Slinger on May 25, 2019 15:51:55 GMT
You'd rather it creep up on you? I'd definitely prefer not to see it coming. |
|
|
|
Post by MartinT on May 25, 2019 15:54:37 GMT
It's one of the more subtle updates, with greater use of acrylic to beautify some of it.
I still like Task View, shared with all my devices. Continuing from where I left off on another machine is a proper benefit.
|
|
|
|
Post by Slinger on Jun 12, 2019 20:28:00 GMT
Windows 10 1903 update installed perfectly fine on most of our machines at work and my own machine. However, we found 11 machines that had been upgraded from W7 to W10 barfed over this update and left the machines in a recovery state. So, if you installed vanilla W10, there seems to be no issue. If you upgraded from W7, proceed carefully and make a backup at the very least. Even better, make a vanilla install of W10 as it's very stable like that. So far the 1903 update has been downloading/setting up/installing for over an hour-and-a-quarter. Just thought I'd mention that in case you don't hear from me for the next week or so. |
|
|
|
Post by petea on Jun 12, 2019 20:30:53 GMT
|
|
|
|
Post by MartinT on Jun 12, 2019 20:33:25 GMT
Don't know about wur doomed, but yur doomed!
|
|
|
|
Post by Slinger on Jun 12, 2019 21:27:06 GMT
Two-and-a-quarter hours in and I'm on the Chromebook. Windoze has rebooted (at last) and is now apparently 28% of the way to Nirvana, but may still reboot several times.
|
|
|
|
Post by Slinger on Jun 12, 2019 22:07:55 GMT
And after only three hours from start to finish the PC has completed the installation , I've rebooted it manually, just to "make sure," and everything seems tickety-boo.
|
|
|
|
Post by MartinT on Jun 13, 2019 4:53:59 GMT
Wow - a little more coal in the furnace required, I think? CPU? SSD? RAM?
|
|
|
|
Post by Slinger on Jun 13, 2019 12:58:53 GMT
That's with...
A new Kingston 480GB SSD as my 'C' drive, that I put in to replace the old 240GB Innodisk SSD in April, which was filling up. The processor is an Intel Core i7 7700, and I've got 32 Gb of (Corsair Dominator Platinum) DDR4 DRAM inside.
I've run various benchmarks on the machine since I built it, and it comes out looking pretty good. The only "unusual" thing about it is that it's got 2 x SSD drives now, and 3 x 2Tb SATA III drives.
FWIW that all sits in an MSI Intel Z270 GAMING PRO CARBON 7th mobo.
|
|
|
|
Post by MartinT on Jun 13, 2019 13:05:14 GMT
Did you update to 1903 from 1809? I can't think of a reason why it took so long. You appear to have plenty of horsepower there.
|
|
|
|
Post by Slinger on Jun 13, 2019 13:13:06 GMT
I must admit that, despite all of my joking, I am at a loss to actually come up with a reason why it should take so long. Normally my MS updates are pretty smooth. There was another, smaller, MS update that ran before 1903 but the machine isn't switched on at the moment, and I can't remember what it was. I only ever wait until updates are offered, I never "force" them. I prefer to let some other bugger find out that the latest download from MS catapults your processor out of the top of the machine before I download it.
|
|
|
|
Post by MikeMusic on Jun 13, 2019 13:24:18 GMT
I have an answer.
It's computers init
|
|
