The other day my Microsoft Surface Pro 4 informed me that the Window 10 Creators Update – the first major update since August last year when version 1607 was rolled out – would be … What? Coming soon? Would start downloading in the background? It wasn’t entirely clear, and I too late thought of grabbing a screen shot. Nothing much happened so I forgot about it. But on Good Friday my device informed me that the update was ready to install.
First impression? Microsoft is being conciliatory. After some bad customer relations in recent times over semi-forced upgrades to Windows 10, and some ongoing irritation over the inability to defer maintenance upgrades to a time when one’s deadlines make it practicable, this update certainly started with kindness. It was ready to be installed, I was told, so did I want to go ahead now with a restart? Or wait for some other time? This update, it said, would take longer than usual.
I decided not to wait, but apparently I glided my mouse pointer over the wrong thing and the update screen went away. But it was easy to go to Windows Update in Settings, and there it was: “Feature update to Windows 10, version 1703”. Again, nice language: “This update is ready to install! We need your help deciding when to restart so we can finish up.” Followed by a “Restart now” button or an option to “Schedule the restart”.
The scheduling isn’t open ended. I could set any time for any day up to a week from now. That ought to provide sufficient flexibility for anyone. We all have to sleep sometimes.
But I just clicked “Restart now”. And then there was the wait and the blue “Restarting” screen was displayed with its dots chasing each other around a circle.
My Surface Pro 4 is the lowest specified model available: M3 processor and 4GB of RAM. So it’s not going to be the fastest at upgrading. But it does have a solid state drive, so it’s likely faster than any computer which uses a hard disk drive as its C: drive.
After a couple of minutes a “Configuring update for Windows 10, 16% complete” message appeared. By four and half minutes it reached 35%. Then it did the usual Windows thing of sitting there for a couple more minutes before suddenly racing through 66%, 71%, 81%, 87%. After sitting on 100% for a minute or so (I’m not sure Microsoft and I fully agree on the meaning of 100%), the system rebooted. That was just over nine minutes after the start.