Get Ready for Microsoft Windows 10 Update

Timeline, Focus Assist, and an update to Microsoft Edge, Dictation, and an update to Cortana.

[engine]

Get ready for the next Windows 10 update about to hit your machines.

You can look forward to Timeline, Focus Assist, and an update to Microsoft Edge, Dictation, and an update to Cortana.

No doubt your machine will be busy for a while during the update.

[blogs.windows.com...]

[keyplyr]

I'm ready... making popcorn.

Wondering if both my Windows devices will update in unison this time. They never have, despite both running Win 10 Pro and being on the same IP.

[IanCP]

Still waiting

[bhukkel]

You have to check updates manually or wait till 8th of May to receive it automaticly.

[robzilla]

Installation was fairly quick, but I already reverted back to the previous version. Apparently they killed homegroup?

[IanCP]

You have to check updates manually

That makes no difference at all on the Insiders circuit.

[keyplyr]

My desktop is loading the update now as I speak :)

[keyplyr]

When you update to Windows 10, version 1803, you won’t see HomeGroup in File Explorer, the Control Panel, or Troubleshoot (Settings > Update & Security > Troubleshoot). Any printers, files, and folders that you shared using HomeGroup will continue to be shared.

New Workarounds:
Share your network printer [support.microsoft.com]
Share files in File Explorer [support.microsoft.com]

[tangor]

I love it when they fix things that ain't broke. :)

[keyplyr]

If that's what you think they did then you're missing the point of a progressive Universal Windows Platform (UWP) and app development architecture.

[robzilla]

Thanks, keyplyr. Not sure why I could no longer access my shared folders after the update then.

Can't dodge the update anyway, it's already re-installed and waiting for a reboot, so I'll have to figure it out eventually.

[keyplyr]

So on my box, HomeGroup was removed but my shared printer, touch pad & extra monitor all still work. All the stuff I config'd through HomeGroup is still connected.

Going forward I guess we just need to add shared devices differently.

[engine]

I had to update a driver on one machine and this Windows 10 April update downloaded. 1.5 hours to install! Yawn!

[keyplyr]

1.5 hours to install

Really? Is that *just* the installation?

Took about 12 to 15 minutes to download in the background while I was working. Took another 10 for it to set-up. Then it alerted me it was ready. I closed everything and clicked "install." It then took less than 20 minutes to install, shutting down and restarting a couple times.

[RedBar]

A warning for anyone with a 32GB SSD machine!

A 16GB flash drive is not large enough for this update, I assume a 32GB is however I attached a 320GB portable since I had nothing inbetween!

[RedBar]

So far for me on a 32GB Acer Switch, 8 hours and still not updated!

Whomsoever approved 32GB SSDs for WIN 10 needs "their bumps feeling" ... I am being very polite!

There must be millions of machines worldwide that Joe Public cannot update since they simply do not know how to and their machines are sitting there, useless!

This is an utter DISGRACE to both the computer manufacturers and also to Microsoft itself who must have KNOWN how big updates could possibly be.

Don't get me wrong, the machine works extremely well, not at the moment, however 32GB is totally a selling anathema.

Do NOT buy anything with an SSD of less than 128GB for Windows 10.

[keyplyr]

My Surface must have auto-updated overnight. Just turned it on and got the Installed Updates screen.

[RedBar]

I'm at the "classic" stuck at 41% on two machines with four more machines to do at some point. The external drive has stopped flashing altogether therefore I have to assume nothing is being installed.

The machines are usable however will they ever update completely?

[RedBar]

WooHoo ... 24 hours later and I have one up and running, the other has a spinning donut therefore hopefully it is doing something.

Both machines kept stalling at 41% however after reading several forum boards at 41% I turned the machine off, removed any USB drives etc, re-booted and it went back to installing but this time got past 41% then asked for MORE space, so I connected the portable drive and it continued on its merry way to installation and completion.

Having said that I feel it is an appalling situation whereby these drives are, quite simply, far too small to handle a big update. We run these as bare bone machines with no added programmes, or games, therefore anyone using them as an everyday normal machine must be in serious trouble owing to the lack of space.

[Travis]

I did the update (manually). Over a 100 Mb/s connection, it took 1 hour to download. And then 1 hour for the installation. All works fine, I answered "no" to all the questions after the last reboot, and then still had to disable some options in the "privacy" settings.

[RedBar]

So last night, Sunday, after several days of trying with my second machine I decided it was all or nothing, I had to find out why I couldn't create enough space on the C drive for the update. I checked everything and could not see what was taking up the space in APPs, insofar as I could see it was completely stanadard except that the space used was far larger than my other machine yet all the APPs were supposedly the same therefore I changed the view to Sort By Size and BINGO, there was a 7.2GB game my granddaughter had downloaded to the C drive yet was not shown in the APPs list!

Needless to say that after that was deleted everything went very smoothly ... hopefully her game can be installed on the 64GB Micro SD Card, does anyone know if this is feasible before I try it?

[engine]

does anyone know if this is feasible before I try it?

No idea. The only thing you can do is to try it. Some have restrictions and won't run on external storage.

I have been updating win 10 machines and it seemed the first one was the 1.5 hours. Another took about 20 minutes, so it seems to be variable per machine.

[Travis]

I have been updating win 10 machines and it seemed the first one was the 1.5 hours. Another took about 20 minutes, so it seems to be variable per machine.

Are both machines part of your local network? If so, I loosely remember that windows 10 has some kind of feature, to optimize the update of machines within the same local network, may be instead of downloading / unpacking, a machine can fetch some files from an already updated one. Or something like that.

[keyplyr]

@engine - I see devices updating differently all the time. My desktop uses DDR while my Surface has SSD. That makes a huge difference in the time the update takes to complete.

[engine]

I shut down the local network aspect of the downloads to avoid having to have all machines running at all times.

The download itself wasn't the big problem, it was time taken to install.

Interestingly, there was another update just today, so it must be correcting some bugs, but this time is was less than five minutes.

[Travis]

Interestingly, there was another update just today, so it must be correcting some bugs, but this time is was less than five minutes.

I think it's related to some users having problem with Google Chrome.

[keyplyr]

Yeah, I got that additional update as well.

Shortly after, FileZilla SFTP pushed an update says M$ just broke the drag-n-drop so their update was a temporary work-around until M$ fixes it.

So expect another one.

[IanCP]

Mine finally updated, I think it took about 30 minutes. I was doing other things. It had a cuppla restarts.

[topr8]

i don't know how long it took as i set it to update while i was out playing football.

several programmes are not working now though, hopefully will be fixed soon!

[IanCP]

Curiously since that update I have gone back to having file copying problems. These are multi-Gb video files from my set top box over my local network from 10.1.1.251 I have been happily copying for years.

Both File Explorer and Q-Dir 6.99.2 now both give an error code at the end of file copy. I can't find any meaningful information on the code.

Error Code: 0xC00D426A

Quite awhile back I went through the rubbish of file explorer coming to an end of a file copy [actually completed] and then just hanging which locked up file explorer.

Is this another variant?