I do NOT want Win 11 on this machine, but MS Update shows that
Win 11 installtion is "pending restart." I found the huge
update file and deleted it, but Update still thinks installation
awaits a restart. Worst case, I presume that should the system
try to install it will ask me what I want to do. Am I naive?

Is MS forcing W11 these days? :(

Jason <jason_warren@invalid.ieee.org> wrote:
> I do NOT want Win 11 on this machine, but MS Update shows that
> Win 11 installtion is "pending restart." I found the huge
> update file and deleted it, but Update still thinks installation
> awaits a restart. Worst case, I presume that should the system
> try to install it will ask me what I want to do. Am I naive?

--
"[Barnabas and Paul] preached the good news in that city and won a large number of disciples. Then they returned to Lystra, Iconium and Antioch, strengthening the disciples and encouraging them to remain true to the faith." --Acts 14:21-22. Playing BRDs suck in PCs compared 2 DVDs. 2 little Zs last weekend (good 4 yesterday's no fall back 1 hr. or else up since 3 AM again) & 2 many vids & poos this Halloween wk.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

In article <O_ycnU0C1-_J1934nZ2dnZfqnPqdnZ2d@earthlink.com>,
ant@zimage.comANT says...
>
> Is MS forcing W11 these days? :(
>
It showed up as a normal update. I surely didn't ask for it!

On 10/30/2023 7:35 PM, Jason wrote:
> I do NOT want Win 11 on this machine, but MS Update shows that
> Win 11 installtion is "pending restart." I found the huge
> update file and deleted it, but Update still thinks installation
> awaits a restart. Worst case, I presume that should the system
> try to install it will ask me what I want to do. Am I naive?
>

Check the dollar-sign directories in the root of C: for a large
mass of material. The attack might come from there.

For example, on my Win11 machine, C:\$WinREAgent has around
3.5GB of material in it, which I would class as "suspicious".
This could be something related to 23H2, dunno.

You should be using this, and setting it to the release you
want things frozen at. I do not know what happens, when you
assert a policy, mid-way through its execution.

https://www.grc.com/incontrol.htm

W10 22H2 # Then, push the button and apply the value
# In Windows Update dialog area, it should then
# result in the displayed info changing.

take a backup, without shutting down, just in case.

HTH,
Paul

> Check the dollar-sign directories in the root of C: for a large
> mass of material. The attack might come from there.
>
I checked. Only one of the $* directories is of significant size.
$WNDOWS.~BT is 25+ GB!

It seems it exists to permit one to back up the OS version but is
otherwise superfluous. I haven't deleted it, but it occupies more
than 10% of precious SSD space, so I'll happily toss it if that's
safe. Web searches suggest that it is.

Thanks :)

Paul wrote on 30-Oct-23 5:55 PM:
> On 10/30/2023 7:35 PM, Jason wrote:
>> I do NOT want Win 11 on this machine, but MS Update shows that
>> Win 11 installtion is "pending restart." I found the huge
>> update file and deleted it, but Update still thinks installation
>> awaits a restart. Worst case, I presume that should the system
>> try to install it will ask me what I want to do. Am I naive?
>>
>
> Check the dollar-sign directories in the root of C: for a large
> mass of material. The attack might come from there.
>
> For example, on my Win11 machine, C:\$WinREAgent has around
> 3.5GB of material in it, which I would class as "suspicious".
> This could be something related to 23H2, dunno.
>
> You should be using this, and setting it to the release you
> want things frozen at. I do not know what happens, when you
> assert a policy, mid-way through its execution.
>
> https://www.grc.com/incontrol.htm
>
> W10 22H2 # Then, push the button and apply the value
> # In Windows Update dialog area, it should then
> # result in the displayed info changing.
>
> take a backup, without shutting down, just in case.
>
> HTH,
> Paul
>
Fyi..adding some clarification on the 'Target Version' registry key based
on repeatable, successful results in the Enterprise and SMB community
that manage clients on non-domain-ed/non-server connected devices with
Win10 Home and Win10 Pro

The below applies to both Win10 Home and Win10 Pro(retail or OEM) 22H2
devices meeting Win11 specs and offered Win11 in Windows Update.

Win10 Home
=> with a target version unset Windows Update may only offer Windows 11
Home not Win 10 22H2 updates [1]

Win 10 Pro
=> with the targeted version unset Windows update offers Win11 Pro and
offers Win10 22H2 updates[2]

[1] Win10 Home = must have the Product Version and Target version
registry keys set to continue to offer Win10 22H2 updates and prevent
Win11 Home offer

[2] Win10 Pro behaves like expected when the Product Version and Target
version registry keys are set(reg key import/manual add or using GPO
setting) and will only offer 22H2 updates and prevent Win11 Pro offer

When Win11 is offered *and* downloaded started or installing(when shown
installing in Windows Update or Waiting for Restart or even failed to
install Win11 but continues to try to install
=> Setting Product Version and Target version to Windows Windows 10
22H2 will abort the Win11 process, revert the device to Win 10 22H2 and
offer Win10 22H2 and discontinue offer of Windows 11
Note: This applies to both Home and Pro

Worthy of consideration: Before doing any of the above, it would be
appropriate for additional insurance to:
1.Stop the Windows Update and Bits services(It may be necessary to
disable both to prevent Windows restarting them
2. Delete the staging folders
- Software Distribution folder
- “C:\$Windows.~BT” folder
3. Then proceed with configuring the Product and Target version in the
registry or GPO.

As a side comment: Do remember that if Windows 11 is completely installed
booting into Windows 11 and the desire is/was to stay on Windows 10 22H2,
then the only options to return to Win10 22H2 is to:
a. Use the revert option in Windows(available for only 10 days)
b. Restore an earlier Win10 22H2 image
c. Clean install Windows 10 22H2 from media or ISO

Finally, some comments on Enterprise and SMB community feedback information:
- almost all cases of Windows 11 being offered on Windows 10 22H2(Home
and Pro) have been where users, after detailed questioning, have clicked
on the Windows 11 Offer(i.e. not happening automatically)

--
....w¡ñ§±¤ñ

In alt.comp.os.windows-10, on Mon, 30 Oct 2023 22:13:12 -0400, Jason
<jason_warren@INVALID.ieee.org> wrote:

>
>> Check the dollar-sign directories in the root of C: for a large
>> mass of material. The attack might come from there.
>>
>I checked. Only one of the $* directories is of significant size.
>$WNDOWS.~BT is 25+ GB!

Wow. I checked mine in case I was "wasting" 25G and it has 4 files
totally 7K. I guess from what you say because I started with win10 and
and haven't upgraded from win7??

I also have $WNDOWS.~WS and it's 7 files totalling 366K. Bigger but I
don't know why.
>
>It seems it exists to permit one to back up the OS version but is
>otherwise superfluous. I haven't deleted it, but it occupies more
>than 10% of precious SSD space, so I'll happily toss it if that's
>safe. Web searches suggest that it is.
>
>Thanks :)

On 10/30/23 18:35, Jason wrote:
> I do NOT want Win 11 on this machine, but MS Update shows that
> Win 11 installtion is "pending restart." I found the huge
> update file and deleted it, but Update still thinks installation
> awaits a restart. Worst case, I presume that should the system
> try to install it will ask me what I want to do. Am I naive?

If you don't want Win11, how about turning off TPM (or secure boot)?
Then your system won't meet the requirements for Win 11.

--
56 days until the winter celebration (Monday, December 25, 2023 12:00 AM
for 1 day).

Mark Lloyd
http://notstupid.us/

"I am an agnostic; I do not pretend to know what many ignorant men are
sure of." -- Clarence Darrow

On 10/31/2023 2:05 PM, Mark Lloyd wrote:
> On 10/30/23 18:35, Jason wrote:
>> I do NOT want Win 11 on this machine, but MS Update shows that
>> Win 11 installtion is "pending restart."  I found the huge
>> update file and deleted it, but Update still thinks installation
>> awaits a restart. Worst case, I presume that should the system
>> try to install it will ask me what I want to do. Am I naive?
>
> If you don't want Win11, how about turning off TPM (or secure boot)?
> Then your system won't meet the requirements for Win 11.

This is fine, if you know what dependencies your machine has on
the current state of TPM.

Are you using BitLocker ?

Is Secure Boot being used on your OS right now ?

These things matter, if you do not want to break something.

Some people don't even know they should be keeping the recovery
key for their Bitlockered PC. It's because, as the user, they did not
"apply" the Bitlocker, and the operating system (provided by the OEM)
is doing it for them. Which is a stupid and a bad idea.

In corporate settings, for HIPPA compliance, the IT department can
push out Bitlocker to the machines as a solution for preventing
corporate info from falling into the wrong hands. That's an example
of a moderately good usage of it. Normally, the IT staff set up
a "complete packaged solution", so that not only is a laptop Bitlockered,
it also receives automatic backups to a corporate backup system. These
are things an ordinary home user could only dream of -- being in control
of their shit, and properly handling their materials :-/

For as long as it works, this can be used to prevent arbitrary upgrades.
This just sets a few Registry locations. The boxes in the interface,
should automatically populate with the "current" release numbers.
If you click the "Take Control" button, then the release stays
locked to the numbers shown. For example, locking W10 22H2, prevents
W11 from coming in. You can also type in the box, and enter numbers
as you feel is appropriate for the situation (such as temporarily
stopping a casual upgrade W11 22H2 to W11 23H2).

https://www.grc.com/incontrol.htm

Paul

On 2023-10-31 03:13, Jason wrote:
>
>> Check the dollar-sign directories in the root of C: for a large
>> mass of material. The attack might come from there.
>>
> I checked. Only one of the $* directories is of significant size.
> $WNDOWS.~BT is 25+ GB!
>
> It seems it exists to permit one to back up the OS version but is
> otherwise superfluous. I haven't deleted it, but it occupies more
> than 10% of precious SSD space, so I'll happily toss it if that's
> safe. Web searches suggest that it is.
>
> Thanks :)

If Win 11 is ready to reboot and install, I suppose it keeps a copy of
the previous system (w 10) somewhere so that you can revert. I don't
know if it is this directory or not.

--
Cheers,
Carlos E.R.

On 10/31/2023 12:39 PM, micky wrote:
> In alt.comp.os.windows-10, on Mon, 30 Oct 2023 22:13:12 -0400, Jason
> <jason_warren@INVALID.ieee.org> wrote:
>
>>
>>> Check the dollar-sign directories in the root of C: for a large
>>> mass of material. The attack might come from there.
>>>
>> I checked. Only one of the $* directories is of significant size.
>> $WNDOWS.~BT is 25+ GB!
>
> Wow. I checked mine in case I was "wasting" 25G and it has 4 files
> totally 7K. I guess from what you say because I started with win10 and
> and haven't upgraded from win7??
>
> I also have $WNDOWS.~WS and it's 7 files totalling 366K. Bigger but I
> don't know why.
>>
>> It seems it exists to permit one to back up the OS version but is
>> otherwise superfluous. I haven't deleted it, but it occupies more
>> than 10% of precious SSD space, so I'll happily toss it if that's
>> safe. Web searches suggest that it is.
>>
>> Thanks :)

The materials used to be stored in C:\Windows.old , which is what
you would find after a version upgrade.

The dollar folders would normally be used for staging of install materials.
If the dollar folders "got deleted by an adventurous user", they will
be created on demand if such a folder is needed in the future.

It's unclear what happens, when those folders start being used for
non-staging activities. If they don't tell the users what they're doing
(such as via the "Windows.old" name which is at least an attempt at a "hint"),
then chaos will ensue.

Why the dollar folders are created like that, without a framework
for the users to understand what they can and cannot do with them,
that's a mystery to me. Where is the discoverability, of leaving
crap all over the place ? At least the Windows.old, properly labels
moribund material. Even if nobody knows how to handle Windows.old
properly (I certainly didn't, until I made a mistake by trying
to delete it manually for fun).

Note that C:\Windows.old should not be thrown in the Recycle Bin.
There have been materials in there, that resist deletion (even from
Linux you can't do it). The "cleanmgr.exe" utility from Microsoft,
knows how to delete C:\Windows.old. The ten day timer knows how to
delete C:\Windows.old. After ten days, it should be cleaned out
automatically.

Cleanmgr.exe will NOT remove a C:\Windows.old that contains a few
undelete-able remnants. Cleanmgr.exe only wades in there, if it
recognizes the folder as a complete and robust Windows image.
If you create a Windows.old in C: right now, and manually store
"test.txt" in it, cleanmgr.exe will not remove the folder for you.
This is why you should not partially delete it, as cleanmgr refuses
to touch it then.

The same cannot be said for the dollar folders. They are a mystery meat.

$WINDOWS.~BT
$Windows.~WS
$WinREAgent On my Win11 Home, this has 3.25GB of files suited to making an installer DVD

https://www.howtogeek.com/268667/what-is-the-windows.bt-folder-and-can-you-delete-it/

"the $WINDOWS.~BT folder contains your previous Windows installation."
"similar to ... Windows.old folder, which contains files from your previous Windows installation."

I can say I've seen the wad of Windows.old on many occasions. Maybe the two
folders are hardlinked ??? No, that doesn't make sense. I can't say I've
seen 40GB of excess files, only 20GB or so.

"$WINDOWS.~WS folder that contains most of the Windows setup files."

Paul

On 10/31/2023 7:50 PM, Carlos E. R. wrote:
> On 2023-10-31 03:13, Jason wrote:
>>
>>> Check the dollar-sign directories in the root of C: for a large
>>> mass of material. The attack might come from there.
>>>
>> I checked. Only one of the $* directories is of significant size.
>> $WNDOWS.~BT is 25+ GB!
>>
>> It seems it exists to permit one to back up the OS version but is
>> otherwise superfluous. I haven't deleted it, but it occupies more
>> than 10% of precious SSD space, so I'll happily toss it if that's
>> safe. Web searches suggest that it is.
>>
>> Thanks :)
>
> If Win 11 is ready to reboot and install, I suppose it keeps a copy
> of the previous system (w 10) somewhere so that you can revert. I
> don't know if it is this directory or not.
>

Windows.old should be created at the time of installation.

The OS is migrated, preserving Programs and user files.
That means, at least portions of the folder would be needed,
during the preparation of a brand new C:\Windows folder.

Windows.old is not just a Windows folder. It has other materials
in it, besides the original content of the Windows folder.

I expect on devices with small storage (32GB eMMC), they have
other tricks regarding storage. The story has changed with time.
At one time, they were using an overlay file system, which "swells"
as it gets older.

Paul

micky wrote on 31-Oct-23 9:39 AM:
> In alt.comp.os.windows-10, on Mon, 30 Oct 2023 22:13:12 -0400, Jason
> <jason_warren@INVALID.ieee.org> wrote:
>
>>
>>> Check the dollar-sign directories in the root of C: for a large
>>> mass of material. The attack might come from there.
>>>
>> I checked. Only one of the $* directories is of significant size.
>> $WNDOWS.~BT is 25+ GB!
>
> Wow. I checked mine in case I was "wasting" 25G and it has 4 files
> totally 7K. I guess from what you say because I started with win10 and
> and haven't upgraded from win7??
>
> I also have $WNDOWS.~WS and it's 7 files totalling 366K. Bigger but I
> don't know why.
>>
>> It seems it exists to permit one to back up the OS version but is
>> otherwise superfluous. I haven't deleted it, but it occupies more
>> than 10% of precious SSD space, so I'll happily toss it if that's
>> safe. Web searches suggest that it is.
>>
>> Thanks :)

To echo what Paul mentioned, but with brevity.

Those folders on your device are not relevant atm to your installation of
Windows 10 wanting to schedule Windows 11 with a pending restart.

Both of those folders beginning with a $ are safe to delete.

--
....w¡ñ§±¤ñ

In article <uhpj9v$mti0$1@dont-email.me>, nospam@needed.invalid says...
>
> https://www.grc.com/incontrol.htm
>
> W10 22H2 # Then, push the button and apply the value
> # In Windows Update dialog area, it should then
> # result in the displayed info changing.
>
> take a backup, without shutting down, just in case.
>
> HTH,
> Paul

Definitely helped! Just yesterday, Update asked me when
to install Win 11. "Don't do it" was not one of the choices!
incontrol appears to have dissuaded it :-)

On 11/1/2023 12:24 AM, Paul wrote:
> On 10/31/2023 12:39 PM, micky wrote:
>> In alt.comp.os.windows-10, on Mon, 30 Oct 2023 22:13:12 -0400, Jason
>> <jason_warren@INVALID.ieee.org> wrote:
>>
>>>
>>>> Check the dollar-sign directories in the root of C: for a large
>>>> mass of material. The attack might come from there.
>>>>
>>> I checked. Only one of the $* directories is of significant size.
>>> $WNDOWS.~BT is 25+ GB!
>>
>> Wow. I checked mine in case I was "wasting" 25G and it has 4 files
>> totally 7K. I guess from what you say because I started with win10 and
>> and haven't upgraded from win7??
>>
>> I also have $WNDOWS.~WS and it's 7 files totalling 366K. Bigger but I
>> don't know why.
>>>
>>> It seems it exists to permit one to back up the OS version but is
>>> otherwise superfluous. I haven't deleted it, but it occupies more
>>> than 10% of precious SSD space, so I'll happily toss it if that's
>>> safe. Web searches suggest that it is.
>>>
>>> Thanks :)
>
> The materials used to be stored in C:\Windows.old , which is what
> you would find after a version upgrade.
>
> The dollar folders would normally be used for staging of install materials.
> If the dollar folders "got deleted by an adventurous user", they will
> be created on demand if such a folder is needed in the future.
>
> It's unclear what happens, when those folders start being used for
> non-staging activities. If they don't tell the users what they're doing
> (such as via the "Windows.old" name which is at least an attempt at a "hint"),
> then chaos will ensue.
>
> Why the dollar folders are created like that, without a framework
> for the users to understand what they can and cannot do with them,
> that's a mystery to me. Where is the discoverability, of leaving
> crap all over the place ? At least the Windows.old, properly labels
> moribund material. Even if nobody knows how to handle Windows.old
> properly (I certainly didn't, until I made a mistake by trying
> to delete it manually for fun).
>
> Note that C:\Windows.old should not be thrown in the Recycle Bin.
> There have been materials in there, that resist deletion (even from
> Linux you can't do it). The "cleanmgr.exe" utility from Microsoft,
> knows how to delete C:\Windows.old. The ten day timer knows how to
> delete C:\Windows.old. After ten days, it should be cleaned out
> automatically.
>
> Cleanmgr.exe will NOT remove a C:\Windows.old that contains a few
> undelete-able remnants. Cleanmgr.exe only wades in there, if it
> recognizes the folder as a complete and robust Windows image.
> If you create a Windows.old in C: right now, and manually store
> "test.txt" in it, cleanmgr.exe will not remove the folder for you.
> This is why you should not partially delete it, as cleanmgr refuses
> to touch it then.
>
> The same cannot be said for the dollar folders. They are a mystery meat.
>
> $WINDOWS.~BT
> $Windows.~WS
> $WinREAgent On my Win11 Home, this has 3.25GB of files suited to making an installer DVD
>
> https://www.howtogeek.com/268667/what-is-the-windows.bt-folder-and-can-you-delete-it/
>
> "the $WINDOWS.~BT folder contains your previous Windows installation."
> "similar to ... Windows.old folder, which contains files from your previous Windows installation."
>
> I can say I've seen the wad of Windows.old on many occasions. Maybe the two
> folders are hardlinked ??? No, that doesn't make sense. I can't say I've
> seen 40GB of excess files, only 20GB or so.
>
> "$WINDOWS.~WS folder that contains most of the Windows setup files."
>
> Paul
>
>
>
I thought you could delete the C:\windows\softwaredistribution folder to
kill a pending update?

On 11/2/2023 6:34 PM, Big Al wrote:
> On 11/1/2023 12:24 AM, Paul wrote:
>> On 10/31/2023 12:39 PM, micky wrote:
>>> In alt.comp.os.windows-10, on Mon, 30 Oct 2023 22:13:12 -0400, Jason
>>> <jason_warren@INVALID.ieee.org> wrote:
>>>
>>>>
>>>>> Check the dollar-sign directories in the root of C: for a large
>>>>> mass of material. The attack might come from there.
>>>>>
>>>> I checked. Only one of the $* directories is of significant size.
>>>> $WNDOWS.~BT is 25+ GB!
>>>
>>> Wow.  I checked mine in case I was "wasting" 25G and it has 4 files
>>> totally 7K.  I guess from what you say because I started with win10 and
>>> and haven't upgraded from win7??
>>>
>>> I also have $WNDOWS.~WS and it's 7 files totalling 366K.  Bigger but I
>>> don't know why.
>>>>
>>>> It seems it exists to permit one to back up the OS version but is
>>>> otherwise superfluous. I haven't deleted it, but it occupies more
>>>> than 10% of precious SSD space, so I'll happily toss it if that's
>>>> safe. Web searches suggest that it is.
>>>>
>>>> Thanks :)
>>
>> The materials used to be stored in C:\Windows.old , which is what
>> you would find after a version upgrade.
>>
>> The dollar folders would normally be used for staging of install materials.
>> If the dollar folders "got deleted by an adventurous user", they will
>> be created on demand if such a folder is needed in the future.
>>
>> It's unclear what happens, when those folders start being used for
>> non-staging activities. If they don't tell the users what they're doing
>> (such as via the "Windows.old" name which is at least an attempt at a "hint"),
>> then chaos will ensue.
>>
>> Why the dollar folders are created like that, without a framework
>> for the users to understand what they can and cannot do with them,
>> that's a mystery to me. Where is the discoverability, of leaving
>> crap all over the place ? At least the Windows.old, properly labels
>> moribund material. Even if nobody knows how to handle Windows.old
>> properly (I certainly didn't, until I made a mistake by trying
>> to delete it manually for fun).
>>
>> Note that C:\Windows.old should not be thrown in the Recycle Bin.
>> There have been materials in there, that resist deletion (even from
>> Linux you can't do it). The "cleanmgr.exe" utility from Microsoft,
>> knows how to delete C:\Windows.old. The ten day timer knows how to
>> delete C:\Windows.old. After ten days, it should be cleaned out
>> automatically.
>>
>> Cleanmgr.exe will NOT remove a C:\Windows.old that contains a few
>> undelete-able remnants. Cleanmgr.exe only wades in there, if it
>> recognizes the folder as a complete and robust Windows image.
>> If you create a Windows.old in C: right now, and manually store
>> "test.txt" in it, cleanmgr.exe will not remove the folder for you.
>> This is why you should not partially delete it, as cleanmgr refuses
>> to touch it then.
>>
>> The same cannot be said for the dollar folders. They are a mystery meat.
>>
>> $WINDOWS.~BT
>> $Windows.~WS
>> $WinREAgent   On my Win11 Home, this has 3.25GB of files suited to making an installer DVD
>>
>> https://www.howtogeek.com/268667/what-is-the-windows.bt-folder-and-can-you-delete-it/
>>
>>    "the $WINDOWS.~BT folder contains your previous Windows installation."
>>    "similar to ... Windows.old folder, which contains files from your previous Windows installation."
>>
>> I can say I've seen the wad of Windows.old on many occasions. Maybe the two
>> folders are hardlinked ???   No, that doesn't make sense. I can't say I've
>> seen 40GB of excess files, only 20GB or so.
>>
>>     "$WINDOWS.~WS folder that contains most of the Windows setup files."
>>
>>     Paul
>>
>>
>>
> I thought you could delete the C:\windows\softwaredistribution folder to kill a pending update?

There is a script which demonstrates some of the details for that.

https://www.tenforums.com/tutorials/24742-reset-windows-update-windows-10-a.html

The purpose of looking at the script (use the scroll bar), is to see
which services are "live" and may lock some item on you. They rename SoftwareDistribution
in the example, presumably so you could undo your handiwork, but in your
case, you could delete it instead.

You could work on the folder in question, from the Macrium File Explorer
on a rescue CD, moving stuff out of there or whatever. And since the
system is at rest, no services would be running. I make that suggestion
for the people who would only destroy stuff from their Linux Live USB stick :-)

Obviously, not every step in there is for a "cleaning", but things like
qmgr treatment, would be so the BITS or DoSVC things are roughly aligned
with your cleaned-out thing.

The Windows Update troubleshooter from Microsoft, its internal script
will include some of the same steps.

As for "damaging" Windows state info, it has become reasonably difficult
to make Windows "forget" what its doing. It analyzes the WinSxS side by side
folder, compares to WSUSSCN2-like materials, to see what needs to be done.
The other subsystems are presumably re-startable if damaged. So even if
you're clumsy, I don't see a reason to permanently damage it :-)

Re-registering the DLLs is part of potential recovery, but it's hard
to say how it would ever have gotten un-registered, unless the user
has been doing that. I have never bothered with such a step when
I've been screwing with it. On WinXP, I would regularly un-register
zipfldr and cabextract, to switch off the integration of those
files as folders. The system used to put those back, on some trigger.

Paul

In alt.comp.os.windows-10, on Thu, 2 Nov 2023 18:21:29 -0400, Jason
<jason_warren@INVALID.ieee.org> wrote:

>In article <uhpj9v$mti0$1@dont-email.me>, nospam@needed.invalid says...
>>
>> https://www.grc.com/incontrol.htm
>>
>> W10 22H2 # Then, push the button and apply the value
>> # In Windows Update dialog area, it should then
>> # result in the displayed info changing.
>>
>> take a backup, without shutting down, just in case.
>>
>> HTH,
>> Paul
>
>Definitely helped! Just yesterday, Update asked me when
>to install Win 11. "Don't do it" was not one of the choices!
>incontrol appears to have dissuaded it :-)

When Greed comes to tempt young men into a life of crime, is "Don't do
it" one of the choices?

When Satan comes to tempt young women into a life of sin, is "Don't do
it" one of the choices?

Don't expect more from Microsoft.