Replies

On the flip side I do receive e-mails from Microsoft themselves that are sent to my work account (that’s been moved to Office 365 some time ago) that get classified mercilessly as SPAM and end up in JUNK folder.

So there’s that.

(Having just thought about it there’s some seed of truth in it though: they are indeed actually a bit junky, so perhaps this service actually works as expected…?!)

b wrote:

krzemien wrote:

… none of this is of any genuine value…

Value is in the eye of the beholder, Shirley?.

anonymous wrote:

Who knows, maybe one in a billion people actually find it useful.

That must be me!

And don’t call me Shirley 😉

But seriously, let’s dissect all these:

1. Windows Hello – well, my SONY Xperia Z on some Android OS was capable of doing the same back in 2012. That’s 8 years soon. Hardly innovative.
And no, don’t need that gimmick, especially on a home PC.

2. Link your phone :@ PC – my PowerBook was capable of doing the same back in 2005 if memory serves. That’s 15 years soon. Hardly innovative either.
And no, don’t need that gimmick as well.

3. Pick up where you left… – and pray: why would I ever need to do that? Sounds messy to me when sync goes wrong (and it inevitably one day will – as my experiences with Garmin devices prove it)

4.Office 365 – thanks, but no: thanks. I am not going to indefinitely and recurrently pay for something I should be able to buy and pay once for (or was able to as this no longer is an option). Also, latest Office 365 does not offer anything new than Office 2003 or 2007 Suites had on offer.

5. OneDrive Cloud protection – where do I begin? If it needs to be safe, it needs to be stored off-line. Also, others do this as well – and FoC – and for quite some time either.

1 user thanked author for this post.

Elly

Yeah, once I un-paused updates and installed the latest lot yesterday got this after reboot and logging in as well – and twice, on two separate user’s account on the same PC.

‘Skip’ is the way forward, obviously – and I cannot help but wonder what Microsoft will make out of the users’ responses as none of this is of any genuine value…

1 user thanked author for this post.

WildBill

Lost for words, obviously! Where is the ‘edit’ button when one needs it…

I’m simply lost of words…

Alas! Are they still on ver 0.x something? With such cadence and momentum release v1 with almost no bugs can be tentatively scheduled sometime in early 2030, methinks?

1 user thanked author for this post.

Mr. Austin

For what it’s worth: this update got installed itself along the Feb CU on my HP OMEN 870-095na two days ago and without any artefacts or side-effects either (well, my PC was definitely operational as usual earlier today).

Although my OS disk is a clone of a clone of an original SSD that came with this PC from factory – with OS partition only expanded each time accordingly – I have never had any serious inclination to tinker with boot records / UEFI partition, or with related UEFI/BIOS settings either (Secure Boot remains enabled etc.).

1 user thanked author for this post.

cmptrgy

[krzemien]

Also these little nuggets are present:

https://support.microsoft.com/en-gb/help/4524244/security-update-for-windows-10-february-11-2020

https://support.microsoft.com/en-gb/help/4502496/security-update-for-windows-10-version-1507-windows-8-1-rt-8-1-server

Addresses an issue in which a third-party Unified Extensible Firmware Interface (UEFI) boot manager might expose UEFI-enabled computers to a security vulnerability.

It does look that all supported Windows versions are affected & addressed – except 1909. Nice.

• This reply was modified 5 years, 2 months ago by krzemien.
• This reply was modified 5 years, 2 months ago by krzemien.

2 users thanked author for this post.

rc primak, woody

Woody, if that’s an answer in a kind-of roundabout way: to this day I just don’t know / am not sure why my current PC:

1. was crashing randomly when I got it in Jan ’17 – from 1607/1703/1709 onwards. Sometime it was days between sudden BSODs, sometime every couple of hours. With no pattern and clear cause at all.
2. suddenly stopped crashing late Oct ’18 on its own – just like that – literally days prior to me moving to 1809. And has never crashed ever since, also with 1903 and 1909 on-board. Never. And nothing has changed hardware-wise either.

And I’m not that bad at troubleshooting, usually have enough lasting patience and perseverance to pursue such nuisance. But not this time.

It’s almost as if 3rd Party and its invisible hand was involved on the way and was fiddling / fine tuning some stuff behind the scenes – and found the reasons that led to these instabilities, and fixed them for me one day.

Just saying.

Surprised that you are surprised taking into account what’s been going on in the last few years.

Is this not a natural and inevitable conclusion that what’s possible in – say, as an example – Android world, where there’s a lot going on behind our backs, is possible here as well? And that’s exactly what Microsoft is ruthlessly doing here by merely applying the same model. Formal release schedules – all this A/B/C/D nonsense – do not matter really at all as they’re mere smoke and mirrors for the Great Unwashed and their joy.

Yes, you’re not in charge of this software and its build/configuration any more.

What’s the alternative though?

Large corporation users – like myself – have merely been moved to 1809 in the recent weeks.

I’m on build 10.0.17763.864 myself.

2 users thanked author for this post.

woody, GreatAndPowerfulTech

My Windows 8.1 x64 HOME on VAIO laptop got updated and works without issues.

Windows 10 x64 HOME deferred until later for the time being – possibly until coming weekend.

…hence I cherish and enjoy – and protect very much either – my March 2017 deployment on this PC that have been updating and upgrading on its own without – luckily – any bigger difficulties and for three years either (barring the unexplained to this day mysterious glitch around upgrade to 1903 that messed up data in WinSxS – which I found out about some weeks later and luckily did manage to fix manually).

I think the problem that Susan raised is two-fold:

1. It’s just not true that you’d never be more than 2 patches away from fully patched unfortunately. As just proven by Susan and my little side-exercise. Otherwise any such upgrade should be a seamless doddle.
2. Not being able to control patching since Windows 10 inception was a very bad and doomed idea. My 1607 deployment was bombarded upfront with various numerous patches preceding 1809/1903 feature upgrade, all being deployed simultaneously and without any user’s control or input. Which ground my PC to a halt for at least an hour and left me wondering if it ever recovers from this state

Just my two-pence.

This is HP machine and I’d rather have its configuration – if I need to – restored to factory state via suitable and provided Recovery Media. Otherwise PC becomes unsupportable in case issues arise (putting aside what I think about HP Support for that matter).

So no, this option is out and I don’t even consider it.

Yeah…

Had utmost pleasure of trying to restore back to 1607 via HP Recovery Media recently and then subsequently discovering that it’s quite a journey to get me to 1909, with few sizeable patches and feature upgrades to 1803/1809 popping up in Windows Update.

So yes, I was equally unimpressed (and also abandoned this route entirely).

How is this different (better) from that:

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/clean-up-the-winsxs-folder

Either by running scripts/commands via Powershell or executing them via Disk Clean-up?