Solved Who didn't see this coming?

Josey Wales said:

Click to expand...

thanks for the link to "do not spy" 11. its installed and a few more settings are now disabled.
many thanks, Steve ..

Q: Who didn't see this coming?

A: I didn't see this coming. I thought for sure, that Microsoft was gonna say: "We were just kidding, you can all use whatever version of Windows you like, as long as you want. And, best of all we will keep supporting it".


Guess I was wrong.

Josey Wales said:

The Video in Post 44 is more relevant. The Problem is that many users are losing Trust in Microsoft. Once that happens it is hard to regain.

Click to expand...

The video in post 44 is even worse than the advertisement video. In fact, as DennyZenny pointed out, there's another video from Titus about three weeks later, where he walks back some of what he said in the October 9 video. But even the newer video is wrong.

In the October 30 video, Titus says that the feature (meaning Recall) is "there and enabled." You can see in his terminal window that the feature is in a Disabled state. That's on the screen while he's saying it's enabled. He also couldn't find a binary running; well duh, the feature is disabled on that system.

He later comments that they can safely remove Recall by fixing a package manifest, adding a dependency on the CBS package to the File Explorer one. They can now "remove Recall safely, without breaking File Explorer." It's a "cool fix, but kinda ridiculous" that they had to do it. Well right, or you could stop messing around in system folders under the guise of making Windows a tiny bit smaller.

I've disabled Recall in a few builds that are now in production without issue. It's a very simple process that does not require manipulating app manifests. I don't want to disparage Titus in general, but on this Recall business, it's hard to imagine how he could be more wrong.

T

Josey Wales said:

The problem is that a user should be able to use a build for as long as the user wants to. There are people still using Windows 7. If a user wants to take that risk so be it. MS will not stop users from using it, they just will not support it.

Click to expand...

They can still run older Windows versions. Just because the older builds won't get updates doesn't mean the OS will stop working. The worst I see is that they won't be able to download older version to do clean or repair installs.

Winuser said:

T

They can still run older Windows versions. Just because the older builds won't get updates doesn't mean the OS will stop working. The worst I see is that they won't be able to download older version to do clean or repair installs.

Click to expand...

I'm not concerned so much about downloads.

New activations could be an issue.

Does MS still allow activations of XP?

YouTube videos can be taken down. I’ve posted some that became outdated and took them down. Also the issue is not just with the old video, as I said. The newer video is wrong also.

And btw, the advertisement video I mentioned was for the other utility. I wasn’t referring to ads on Titus’ channel. I’m not opposed to people making money, especially me.

This thread has devolved into 2 completely separate topics. Watermark and Recall.

bobkn said:

Does MS still allow activations of XP?

Click to expand...

That's a good question and one I can't answer. I will say this. IMO, If we want to go forward with technology there's going to be a time that we have too say goodbye to the old. I loved my first computer. It was an Atari 800XL. With tech moving forward I knew that to keep up I had to say goodbye to it.

Winuser said:

That's a good question and one I can't answer. I will say this. IMO, If we want to go forward with technology there's going to be a time that we have too say goodbye to the old.

Click to expand...

I understand based on unconfirmed reporting online that there are reasons that MS are changing system requirements. Apparently one is that the Windows coders are finding it increasingly difficult bearing in the mind the pace of change in technology to keep Windows as backward compatible as it has in past.

BamaInArk said:

This thread has devolved into 2 completely separate topics. Watermark and Recall.

Click to expand...

The guy who introduced Recall to this discussion has made his final and last statement (several times).

So now Microsoft says this ...


Per Microsoft TPM 2.0 is now a "non negotiable" requirement to run Windows 11.

So my older, perfectly fine 128GB 8core Xeon 3.7GHz CPU box with TPM 1.2 won't run Windows 11 in the future when Microsoft enforces the TPM 2.0 mandate.

So definitely sticking with Windows 10 for now. Why try the magic tweaks to go to Windows 11 when Microsoft tells me in the future it will refuse to boot (probably).

Funny I can run Windows 11 perfectly fine in VirtualBox 7.1.X on my Windows 10 TPM 1.2 system where I can configure VirtualBox to have a (simulated) TPM 2.0 device.

So Microsoft, why can't you just take the TPM 2.0 code and put it into Windows 11 and stop the 'forced upgrade' nonsense of perfectly fine older running hardware.