"Some settings are managed by your organization" and OS is out of date.
I've been working on reinstalling Windows 10 Pro on a Lenovo laptop L440 and suddenly I'm getting this in Settings/Update & Security
The Windows installation reports: Version 1709 16299:125
This was installed with the latest download from Microsoft > .iso > DVD
First, it was run booting from the DVD and installing Windows from scratch with an all new partition(s).
Then it seemed to "break" with the Cortana icon not working and no "fix" for that.
So then it was run from within Windows, Saving Files and App's - which seemed to fix things.
But now.... (as above).
I notice that another systems (that have been around for a while) are showing:
Version 1709 16299:248
Anyway, I need this computer to be up-to-date and capable of getting updates and managing updates in the most reasonable way possible because I'm going to be using it as a test platform in the near term.
So, it seems to suggest that the existing sytem is more up-to-date than the "new" install I just did.
Perhaps that has something to do with this issue: "Some settings managed by your Organization"
I've read about it and it appears that its' a bug.
The suggested "fixes" using gpedit, etc. don't do a thing.
I'd be tempted to say that I'd like to get to :248. Does that seem reasonable?
How?
"Some settings managed by your Organization"It appears that there are no updates waiting to happen.
The Windows installation reports: Version 1709 16299:125
This was installed with the latest download from Microsoft > .iso > DVD
First, it was run booting from the DVD and installing Windows from scratch with an all new partition(s).
Then it seemed to "break" with the Cortana icon not working and no "fix" for that.
So then it was run from within Windows, Saving Files and App's - which seemed to fix things.
But now.... (as above).
I notice that another systems (that have been around for a while) are showing:
Version 1709 16299:248
Anyway, I need this computer to be up-to-date and capable of getting updates and managing updates in the most reasonable way possible because I'm going to be using it as a test platform in the near term.
So, it seems to suggest that the existing sytem is more up-to-date than the "new" install I just did.
Perhaps that has something to do with this issue: "Some settings managed by your Organization"
I've read about it and it appears that its' a bug.
The suggested "fixes" using gpedit, etc. don't do a thing.
I'd be tempted to say that I'd like to get to :248. Does that seem reasonable?
How?
John
Open Settings , Updates, and run updates manually. That should work ( it does for me ) and may also turn the warning off
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
arnold: There is no domain and no GPO that applies.
John Hurst: There is no option to check updates as one would normally expect.
Is everyone aware of this bug?
John Hurst: There is no option to check updates as one would normally expect.
Is everyone aware of this bug?
As I suggested, run updates manually and that should make this warning go away. Otherwise, it will wait until updates are in widespread use
Also what you are seeing is by design and not a bug
What else do you have installed on this system that potentially overwrites the update setting.s
Run mmc, open group policy related to local policy, see if that is set
Are you using a local login, or a Microsoft login, if you use a work related email address as a Microsoft login, that would mimic the behavior as the system will "join" the online based restrictions...
Run mmc, open group policy related to local policy, see if that is set
Are you using a local login, or a Microsoft login, if you use a work related email address as a Microsoft login, that would mimic the behavior as the system will "join" the online based restrictions...
ASKER
arnold: There are no online based restrictions that I know of. Uses a local login.
Nothing should have overwritten the update settings.
John Hurst: Well, my research keeps finding that it *is* a bug and suggests that it's meaningless. But I can't tolerate it even so.
Have you looked into the recommended "fixes"? It involves setting (and hence unsetting):
gpedit
Computer Configuration
Administrative Templates
Windows Components
Data Collection and Preview Builds
Allow Telemetry - Enabled / 3-Full
Installing 16299.248 by downloading and installing seems to get rid of it. Is that what you meant by "manually" doing updates and NOT pressing the check for updates button?
Nothing should have overwritten the update settings.
John Hurst: Well, my research keeps finding that it *is* a bug and suggests that it's meaningless. But I can't tolerate it even so.
Have you looked into the recommended "fixes"? It involves setting (and hence unsetting):
gpedit
Computer Configuration
Administrative Templates
Windows Components
Data Collection and Preview Builds
Allow Telemetry - Enabled / 3-Full
Installing 16299.248 by downloading and installing seems to get rid of it. Is that what you meant by "manually" doing updates and NOT pressing the check for updates button?
Yes manually download , update, restart and then test
ASKER
John Hurst: What process would you use to determine just *what* to download?
I just Windows update and run it, the restart as required.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Run gpresults /V and see.
At this point, all I can do is guestimate what your situation might be. Check the settings, update and the track/style this system is on.
Unfortunately, having no access to your system, your responses to my suggestions that they do not apply, but provide little info on what to base.
Double check the settings of the system if it is a pro version that it was not inudvertantly joined to an ms online domain through the use of a Microsoft online account.
At this point, all I can do is guestimate what your situation might be. Check the settings, update and the track/style this system is on.
Unfortunately, having no access to your system, your responses to my suggestions that they do not apply, but provide little info on what to base.
Double check the settings of the system if it is a pro version that it was not inudvertantly joined to an ms online domain through the use of a Microsoft online account.
ASKER
I believe I've found the source of the problem:
When doing a clean install, one is asked if the install is for personal use or a company.
The wrong answer (company) will result in what I was seeing it appears.
How one is supposed to "fix" that is more than I know.
So you were both right about that but I was unable to understand what you said at first.
Thanks!
When doing a clean install, one is asked if the install is for personal use or a company.
The wrong answer (company) will result in what I was seeing it appears.
How one is supposed to "fix" that is more than I know.
So you were both right about that but I was unable to understand what you said at first.
Thanks!
I think that is in line with my comment that Microsoft would set the "Wait for widespread use" . This would be particularly true for Companies as the IT department would want to test first. If Company, you would change the setting if you want more immediate updates. The setting also started to appear this year (2018) after the problems with many machines.
So I think what you are seeing is "Situation now normal" and not a bug.
So I think what you are seeing is "Situation now normal" and not a bug.
ASKER
Thanks again!
You are very welcome. Thanks for the update and once again, I like to help you whenever I can.
ASKER
Yes, situation "normal" and not a bug. I should be more careful where I "research".