Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing
-
This happened last week but I'm still fuming about it. I came into work and all but 6 or so of our Windows 10 Pro 1803 systems had upgraded to 1809. I had been planing to wait a while before upgrading so this was completely unexpected.
I have a WSUS server properly set up and the Feature update to 1809 was not approved at all. Googling around, I discovered that there's something called "Dual Scan" and running this check has shown me that I in fact have Dual Scan enabled. I can not disable it apparently since we are not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.
Has anyone else dealt with this? Any suggestions?
-
Welcome to the wonderful world of Windows.
-
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.
We have WSUS with Windows 10 1803 professional and we do not have DUal Scan so they will not upgrade until approved.
-
@dbeato said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.
We have WSUS with Windows 10 1803 professional and we do not have DUal Scan so they will not upgrade until approved.
Yeah, same here... however, I also have a group policy enabled company wide that strictly blocks OS upgrades. When I approve them in WSUS, then they upgrade. But never before.
My main point is that we have all versions of Win10 running, controlled by WSUS, and they only upgrade when approved in WSUS. There has never been a different result.
-
@Obsolesce said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dbeato said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.
We have WSUS with Windows 10 1803 professional and we do not have DUal Scan so they will not upgrade until approved.
Yeah, same here... however, I also have a group policy enabled company wide that strictly blocks OS upgrades. When I approve them in WSUS, then they upgrade. But never before.
My main point is that we have all versions of Win10 running, controlled by WSUS, and they only upgrade when approved in WSUS. There has never been a different result.
Can you maybe provide me with your settings you applied to prevent that?
-
@dbeato said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.
We have WSUS with Windows 10 1803 professional and we do not have DUal Scan so they will not upgrade until approved.
Can you explain how you disabled Dual Scan? Right now it seems like the only way is by adding those registry settings..
-
This post is deleted! -
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@Obsolesce said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dbeato said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.
We have WSUS with Windows 10 1803 professional and we do not have DUal Scan so they will not upgrade until approved.
Yeah, same here... however, I also have a group policy enabled company wide that strictly blocks OS upgrades. When I approve them in WSUS, then they upgrade. But never before.
My main point is that we have all versions of Win10 running, controlled by WSUS, and they only upgrade when approved in WSUS. There has never been a different result.
Can you maybe provide me with your settings you applied to prevent that?
-
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@Obsolesce said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dbeato said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.
We have WSUS with Windows 10 1803 professional and we do not have DUal Scan so they will not upgrade until approved.
Yeah, same here... however, I also have a group policy enabled company wide that strictly blocks OS upgrades. When I approve them in WSUS, then they upgrade. But never before.
My main point is that we have all versions of Win10 running, controlled by WSUS, and they only upgrade when approved in WSUS. There has never been a different result.
Can you maybe provide me with your settings you applied to prevent that?
-
@Obsolesce said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@Obsolesce said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dbeato said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.
We have WSUS with Windows 10 1803 professional and we do not have DUal Scan so they will not upgrade until approved.
Yeah, same here... however, I also have a group policy enabled company wide that strictly blocks OS upgrades. When I approve them in WSUS, then they upgrade. But never before.
My main point is that we have all versions of Win10 running, controlled by WSUS, and they only upgrade when approved in WSUS. There has never been a different result.
Can you maybe provide me with your settings you applied to prevent that?
I've been using this policy since 11/18/2015 and has worked 100% ever since. My last modification was 6/10/2016, though I don't remember what that was.
-
I don't have @Obsolesce settings in place, and none of my machines did this Dual Scan thing.
-
@Obsolesce said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@Obsolesce said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dbeato said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.
We have WSUS with Windows 10 1803 professional and we do not have DUal Scan so they will not upgrade until approved.
Yeah, same here... however, I also have a group policy enabled company wide that strictly blocks OS upgrades. When I approve them in WSUS, then they upgrade. But never before.
My main point is that we have all versions of Win10 running, controlled by WSUS, and they only upgrade when approved in WSUS. There has never been a different result.
Can you maybe provide me with your settings you applied to prevent that?
hmm.. I can give that a try but when I searched"GWX" it looks like it was meant to prevent Windows 7/8/8.1 systems from upgrading to Windows 10.
-
@Dashrender said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
I don't have @Obsolesce settings in place, and none of my machines did this Dual Scan thing.
I had a few Windows 10 machines that didn't upgrade either and I don't really know why. Some of them were the same Windows 10 images as the other ones that upgraded, so idk.
-
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@Dashrender said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
I don't have @Obsolesce settings in place, and none of my machines did this Dual Scan thing.
I had a few Windows 10 machines that didn't upgrade either and I don't really know why. Some of them were the same Windows 10 images as the other ones that upgraded, so idk.
What are the chances (and I don't care what JB says - I don't agree) that those three had an image from VLSC media, and the rest are from the publicly available Windows 10 media?
When I build an install USB from the Public media - I only get the option to install Home or pro. When I build an install USB from the VLSC media - I get Enterprise/Pro/Pro for workstations/Education/Home. There is a difference.
Also WSUS sees a difference between consumer and business
I do not have any Windows 10 Home on my network, so when it's talking about consumer, I'm assuming it's talking about OEM or publicly available media used for install. -
@Dashrender said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
I do not have any Windows 10 Home on my network, so when it's talking about consumer, I'm assuming it's talking about OEM or publicly available media used for install.
Correct
-
This is what I have to prevent my clients from communicating to Microsoft Update servers:
-
-
-
@travisdh1 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@IRJ said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
https://media.makeameme.org/created/now-witness-the-xeedgd.jpg
Quick, before it gets blown up!
I could totally see Microsoft building a battle station the size of a small moon. Then not worrying about a vulnerability the size of a womprat that blows the entire thing up.
-
@Dashrender said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
@Dashrender said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:
I don't have @Obsolesce settings in place, and none of my machines did this Dual Scan thing.
I had a few Windows 10 machines that didn't upgrade either and I don't really know why. Some of them were the same Windows 10 images as the other ones that upgraded, so idk.
What are the chances (and I don't care what JB says - I don't agree) that those three had an image from VLSC media, and the rest are from the publicly available Windows 10 media?
When I build an install USB from the Public media - I only get the option to install Home or pro. When I build an install USB from the VLSC media - I get Enterprise/Pro/Pro for workstations/Education/Home. There is a difference.
Also WSUS sees a difference between consumer and business
I do not have any Windows 10 Home on my network, so when it's talking about consumer, I'm assuming it's talking about OEM or publicly available media used for install.All of these systems were Dell OptiPlex systems (bundled with Windows 10) but then I used a VLSC Windows 10 image with MDT to image them all. Most of these were all upgraded automatically but there was 1 or 2 that did not.
I know that one of the systems was a consumer version of Windows 10 which the previous tech installed - no idea where he got it.
