[SOLVED] Why am I getting preview updates?

Hi, hope you can help enlighten me.
Why am I getting preview updates? I am not signed up as an insider.. as far as I am aware I do not have any options ticked to say I want them.
In fact... the normal Cumulative update previews seem to work as expected.. i.e. I see them as avail.. but I dont get them..
But the .NET Framework ones seem to come through if I use the "check for updates" button in windows update.
So it seems illogical that they working differently..
Anyone any idea whats go on? I dont want any preview/Beta updates on my main PC..

As you can see from screen shot... the .NET update is progressing.. and the cumulative update is not (all I did was use the "check for updates" button)
Here is link to screen shot.. (for some reason I could not embed in the message ... Toms FUBAR)
https://1drv.ms/u/s!Asw-ZJYHTEcTgqYprCnfvs5kqj-FLQ
 
  • Like
Reactions: Shawn Eary
Solution
Previews are (non-security) bug fixes release on the 3rd/4th week of every month (so-called C/D releases). If you don't install it, those bug fixes will be lumped together in next month's patch Tuesday security fixes.

https://answers.microsoft.com/en-us...w/46a14732-18dd-45fd-8829-f65426cd9adc?auth=1

In January win 11 got a .net preview one week and about 10 days later there was another .net update, which was odd.
CU updates are all the rage, WIn 11 got two CU this month so far, one was marked as Preview when I installed it but doesn't show as that in Update history - I did install it manually though, so not sure when it would have been pushed at me. Another update on...
cumulative previews are there for manual updates, its not insider build, they shouldnt install on its own, if you dont do anything, you will get them with regular cumulative updates

Ok.. so why are they behaving differently?
My experience was... when I went to the "Windows update page"... it showed the 2022-02 Cumulative update preview... with the option to "download and install" below..
When I clicked the "Check for updates" .. it found the .NET cumulative update and immediately started to download and install (per the screen shot in my original post).
But the original Cumulative update did not action (again, as you can see in the screen shot)

SO when you say "they shouldnt install on its own, if you dont do anything" .... does just pressing the "check for updates" button mean I "did something"?
It seems crazy.. I dont get to see the .NET update as available, without it installing... that cant be right for what is a preview update?

So it cant be just me... is it broken? working like this for everyone? Its been doing this for months... so why it not fixed?

Sorry.. lots of questions.. but anyone know?
Cheers
 
  • Like
Reactions: Shawn Eary
preview update is pretty much beta, it wont get automatically installed, you wont get it even if you click "check for updates", its for manual update, it does not contain any security updates, just some new features/bug fixes
microsoft releases those for a while now, its there for those who want to try it before it gets released for everybody with normal cumulative update...and yes to get it, you have to click on download and install button
or just ignore it :)

https://techcommunity.microsoft.com...ndows-10-update-servicing-cadence/ba-p/222376
cumulative preview is that C and D release
 
preview update is pretty much beta, it wont get automatically installed, you wont get it even if you click "check for updates", its for manual update, it does not contain any security updates, just some new features/bug fixes
microsoft releases those for a while now, its there for those who want to try it before it gets released for everybody with normal cumulative update...and yes to get it, you have to click on download and install button
or just ignore it :)

https://techcommunity.microsoft.com...ndows-10-update-servicing-cadence/ba-p/222376
cumulative preview is that C and D release

Thanks, but did you read what I said? What you said makes sense.. and how I think it should work... but its not whats happening for the .NET preview updates...

And I just checked my daughters machine (win 11).. and hers behaved exactly the same... the .NET preview immediatly started to download and install when I pressed the "Check for updates"..

So it cant be just me... so is it "broken"?
 
  • Like
Reactions: Shawn Eary
Thanks, but did you read what I said? What you said makes sense.. and how I think it should work... but its not whats happening for the .NET preview updates...

And I just checked my daughters machine (win 11).. and hers behaved exactly the same... the .NET preview immediatly started to download and install when I pressed the "Check for updates"..

So it cant be just me... so is it "broken"?
Seems to be the way it works.
Run it through google many folks fine it annoying.
 
  • Like
Reactions: Shawn Eary
Previews are (non-security) bug fixes release on the 3rd/4th week of every month (so-called C/D releases). If you don't install it, those bug fixes will be lumped together in next month's patch Tuesday security fixes.

https://answers.microsoft.com/en-us...w/46a14732-18dd-45fd-8829-f65426cd9adc?auth=1

In January win 11 got a .net preview one week and about 10 days later there was another .net update, which was odd.
CU updates are all the rage, WIn 11 got two CU this month so far, one was marked as Preview when I installed it but doesn't show as that in Update history - I did install it manually though, so not sure when it would have been pushed at me. Another update on there now but its not being pushed at me yet.
I wouldn't have updated if I knew it was a beta.. although I did use insiders so Win 11 was beta for 3 months while I used it and it was fine, so it is probably okay.

I am guessing but that CU probably includes the changes needed to Fix .net that were in this OOB update in January that wasn't on Windows Update - https://support.microsoft.com/en-au...-of-band-e79a633f-e876-4268-a21e-de6a9ca52da7

its possible its push status is wrong - https://support.microsoft.com/en-au...ion-21h2-c3dd884e-9cd1-4c6e-8d5a-08f6aa9d5ae3
 
Last edited:
Solution
https://answers.microsoft.com/en-us...w/46a14732-18dd-45fd-8829-f65426cd9adc?auth=1

In January win 11 got a .net preview one week and about 10 days later there was another .net update, which was odd.
CU updates are all the rage, WIn 11 got two CU this month so far, one was marked as Preview when I installed it but doesn't show as that in Update history - I did install it manually though, so not sure when it would have been pushed at me. Another update on there now but its not being pushed at me yet.
I wouldn't have updated if I knew it was a beta.. although I did use insiders so Win 11 was beta for 3 months while I used it and it was fine, so it is probably okay.

I am guessing but that CU probably includes the changes needed to Fix .net that were in this OOB update in January that wasn't on Windows Update - https://support.microsoft.com/en-au...-of-band-e79a633f-e876-4268-a21e-de6a9ca52da7

its possible its push status is wrong - https://support.microsoft.com/en-au...ion-21h2-c3dd884e-9cd1-4c6e-8d5a-08f6aa9d5ae3

What? Not sure what you saying
But sounds like no-one has a clear picture of WTF is going on
If a fix is required for a CU... then it a fix that gets immediately pushed... it should not be marked as "Preview", even if the original patch it fixing was preview...
If its a fix for a preview, if you installed the preview.. you get the fix... thats fair enough..
But dont then mark the fix as "preview"...

So.. to summarise no-one seems to be able to explain (beyond MS <Mod Edit> up) .... why I got a forced preview update...
Correct? or have I misunderstood anyone?
 
Last edited by a moderator:
  • Like
Reactions: Shawn Eary
Thanks, I do appreciate people are trying to help... but by same token, it does not help when people suggest things that clearly dont fit the evidence that I was careful to try and provide. The next person then starts answering a different question and it just descends in confusion.

My comment that "no-one has a clear picture of WTF is going on" was a reflection on Microsoft (because as you say - they dont seem to be consistent with their actions).. so its no surprise no-one here can give a solution.
But even a nice clear.... "Yes.. Microsoft are not working correctly here.. and its not in line with how its supposed to work... but we all experiencing the same issue".... would be a perfectly succinct and full reply.
Cheers
 
  • Like
Reactions: Shawn Eary