Something to think about...

I don’t often boot my PC, it spends its off time in standby mode.
I had to reboot it recently.
It took my PC nearly two minutes to reboot.

With the processor running at 1.6GHz. And it’s a fake dual-core (Atom hyperthreading such and such). Let’s multiply that by 1.5 because it isn’t a true dual core. That means a combined clock speed of 2.4GHz, for two minutes.

Which by my calculations is equivalent to ten hours of use of my first RISC OS machine, an A3000.

That is a rough and ready idea of how much processing power it takes to start XP, and XP ain’t exactly cutting edge any more (then, neither is a 1.6GHz Atom…). Even so, try to imagine how many processor cycles the machine burns through just getting itself going. And I thought RISC OS 3 took a long time to get to the Desktop, back in the early ’90s!

This is progress?

Progress is that Windows 10 is much much faster when booting than XP ever was. I have only migrated one PC in our household to Windows 10 (and ran into a nasty networking problem – German speaking readers can read the tale here ), and it boots really fast. Even without an SSD. Nearly RISC OS booting speed.

We’ll have to see if it keeps up the speed once it runs a few years.

https://translate.googleusercontent.com/translate_c?act=url&depth=1&hl=en&ie=UTF8&nv=1&prev=_t&rurl=translate.google.com&sl=auto&tl=en&u=http://itblog.huber-net.de/2016/01/die-windows-10-netzwerk-misere/&usg=ALkJrhgKYvPDSAkJZSdsPAkPC6PnorEJGA

My Win 10 machine will usually boot in around 20 seconds, but sometimes takes 60-90 seconds. I wonder whether it’s something to do with updates, but in any case it’s certainly not quick when it feels like being slow!

I meant to say that your post explained why there’s a difference, I just forgot to include that part :)

So Windows 10 is great unless Microsoft is incompetent and accidently send what everyone else would describe as a virus. Presumably they have a large legal department.

Well – http://m.theregister.co.uk/2016/02/02/microsoft_ups_pressure_win_10_holdouts/

Not a lot between Windows 10 and malware, these days. :-)

Interesting. I have updated to windows 10 but changed back because of graphics driver problems. 8.1 keeps nagging me to change then telling me I can’t because the graphics driver isn’t compatible – most amusing.

There’s a laptop with an update problem sitting at a client’s office waiting for me to look at it when I have more time. The symptoms are that its trying to install an update, gets to x%, then gives up and takes several hours to get back to its previous state.

Until I can look at it, I can only guess – but I suspect this is a Win10 update repeatedly failing.

Thankfully, there’s no rush: there’s a spare machine that the user now has on his desk. Given what they use the computers for, I’m tempted to suggest to the directors that I just kill Windows on the faulty computer and install a Linux on it to see how they get on with that. Which would also mean I’ll get my first foray into the world of Linux using someone else’s hardware instead of my own. ;)

My laptops Win81 partition (it usually runs Ubuntu) has that same problem. The getting back to previous state happened each time I started the machine, and it took a long time. But eventually, after several restarts and something that must have been several hours later, it started again in Windows mode.

Unfortunately I assumed it was the Win10 update, so I hid that, and updated again. But now it’s in the same state… should have checked what was the actual problem… So be warned…