Replies

I pause Windows Updates until the end of the month.  Then I wait for Ask Woody to lower the DEFCON before I un-pause Windows Update.  I do not look to see what the updates might be before I download and install the updates.  And I usually do not look at any MS documentation to see what is contained in each update.

 

“Previews are not mandatory.
On a Pro version they should be blocked using GPEdit.”

The November patch KB5048292 2024-11 Cumulative Preview Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 for x64 was not listed as “Optional”, so I installed it.  I could have done extra work to hide this update.

The November patch KB5046714 2024-11 Cumulative Update Preview for Win 10 22H2 for x64 was listed as optional.  But for some reason, after my reboot and again running Windows Update (to complete the download and installation of the KB5046613 update), Windows Update decided to install the KB5046714  preview update.  I had NOT told WU to install any optional updates.  I do nothing special with optional updates; I look to see what they are, and I ignore them (assuming that they are optional and will not be installed without my explicit action).

 

 

“Never got a “preview” .NET update”

On October 22, 2024 I installed the following update: KB5044091 2024-10 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 for x64

This was a last .NET update that was not marked “Preview”.  And in August: KB5042352 2024-08 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 for x64 .

 

My experiences with the Windows 10 22H2 November updates:

KB5048292 2024-11 Cumulative Preview Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 for x64
KB890830 Malicious Software Removal Tool (Nov2024) MRT.exe

KB5046613 2024-11 Cumulative Update for Win 10 22H2 for x64

First, I have no idea why MS makes the .NET preview patch a mandatory patch.  I had to install it.  MRT installed with no problems, as usual.  But KB5046613 was still downloading (it gets larger each month) when I decided to re-try installing the recent Java update, which has been failing with a 1603 error for a few weeks.  That Java update started a new download, and in the process the download for 6613 stopped.  I had to reboot (due to the .NET update), and then try 6613 again.  6613 installed OK, but Windows Update also installed  KB5046714 2024-11 Cumulative Update Preview for Win 10 22H2 for x6; I did not tell WU to install this Preview update.  The only problem I have seen with the updates is that the update process somehow turned off Windows Defender, and I had to turn it back on in order to get pattern updates.

After I installed the July 2024 patches, my desktop background went from a solid color to some image (that made the icons hard to read).  I have no idea why MS made this change.  For those who need instructions on changing the desktop background:

Settings –> Personalization –> Background

1 user thanked author for this post.

Frwin

“Of course Microsoft can develop 2 versions of API for a/v software, one for EU one for the rest of the world.”  What about a computer that is portable and travels between the EU and the rest of the world?  What version of the software would it need to run?  And the Windows Update process would have to determine what version is running to enable the correct version of a patch to be installed.

Here is more information.  The culprit may be Firefox.  This morning I clicked on a URL in Thunderbird, and Firefox updated.  I assume that Firefox had crashed overnight, but I do not see a FF “crash” window, and I have not looked at FF crash reports.  After FF restarted, my C-disk reported   14,932,058,112 bytes free.  I have a full directory listing from Monday’s incremental backup and from this morning’s full backup.  I have a “diff” listing that I have to research.

I have a problem with free space on my C-drive.  Some unknown process(es) is/are using disk space, and I cannot tell what is happening.  A week ago, I had low disk space messages, and I did nothing; the free space came back.  Look at this:

0 Dir(s) 13,557,297,152 bytes free     03/24 08:30
3 Dir(s)     416,718,848 bytes free      03/27
3 Dir(s)     537,169,920 bytes free      03/27
0 Dir(s)     537,382,912 bytes free      03/27
0 Dir(s)    1,113,702,400 bytes free    03/27
0 Dir(s)    1,106,006,016 bytes free   03/27
0 Dir(s)    1,106,096,128 bytes free   03/27
0 Dir(s)    1,050,591,232 bytes free   03/27
0 Dir(s)      241,594,368 bytes free    03/27
0 Dir(s)     241,975,296 bytes free     03/27

When I did a backup of my C-drive Monday. I had lots of free space.  Between then and today (Wed PM) , the free space has dramatically been reduced.  These lines are from a cmd window “dir” commands, where I have added the date.  Most of the last lines are from tonight, where the free space has dropped from 1 Gb to 241 Mb.  And I have not done anything “extraordinary” that I think might have caused this.  Tomorrow I will power-off my machine to replace the motherboard, and, if I remember, I will get free space listings before and after.  I wonder if there is some Windows 10 process that is storing one or more hidden files on my c-drive.  I do not know if TreeSize has access to hidden files.  I have looked at TreeSize output, and I cannot see any large files that are abnormal.  I will post more tomorrow after the new motherboard is installed.

 

Thanks.  F7 and Esc are the culprit and correction.

That MS web page has details on how to change the color scheme on a CMD window.  I am so used to black background and white text that I see no need to change.  My question is this – what sequence of keystrokes produced the inset window that listed my last commands?

After I have installed (or tried to install) the monthly updates (after AskWoody gives the go-ahead near the end of the month), I pause updates until the end of the next month.  This is to avoid installing updates immediately on the next Patch Tuesday.  So I am not worried about WU trying to re-install the patch.  If MS releases an out-of-band patch, I will read about it via my Internet sources, and then I will resume WU to install it.

I have a basic question – why hide this patch?  Either it installs and does what it is supposed to do (and does nothing harmful), or it does not install (and causes no harm, except for an error message).

On my Win 10 Professional 22H2 system, KB5034441 did not install.  I did not want to go through the bother of increasing the size of the recovery partition, as I have no idea ow much more space it really needs for this patch.  I saw no need to try to hide this patch; if it fails to install, then no harm is done.  If MS comes out with a new patch in February (or subsequent month) – with a different patchID , then Windows Update will try to install it (as a new patch).  If MS releases an update with the same patchID, will Windows Update download the new patch, or will it see that I have already downloaded a patch with this ID and not download the new one?  That is the basic problem with re-releasing a patch with the same ID.  I do not know the Windows Update logic.

The updates are cumulative, so each month the size of the update increases.  When I went to the MS Update catalog to download the December Win 10 22H2 update (see my post below as to why I had to), the resulting .msu file had size 821,354,453.  That is one problem with cumulative updates.

I solved my problem by searching for and viewing a YouTube video on Windows Update tro9ubleshooting: Settings –> Update & Security –> Troubleshoot –> Additional –> Windows Update –> Run the troubleshooter

The troubleshooter said that it found and corrected problem(s); it gave me no details as to what it fixed. After that, I ran the .msu file, and the update installed; winver says Version 22H2 (OS Build 19045.3803).

1 user thanked author for this post.

lmacri