Win10 Home appears to be getting the “Pause Updates” setting

Topic

New Reply

I wouldn’t have believed it if I didn’t just verify it myself. Windows 10 beta build 15002 (and 15007) Home have the “Pause Update” capability, which
[See the full post at: Win10 Home appears to be getting the “Pause Updates” setting]

Reply | Quote

Replies

Please excuse me for making this comment but – will Windows 10 ever get out of “beta” mode? Just speaking for myself, I wouldn’t want to buy a computer with a beta operating system on it. But I suppose most average people don’t know about that. They’re the unknowing “testers”.

Reply | Quote

I agree with Charlie. Windows, whatever they want to call it in the future, is certain to be a perpetual beta. Fix one thing and break another. Herding cats will seem simple.

Reply | Quote

The answer is no. That’s what “the last version of windows means – continuous development live on the users’ copies.

Reply | Quote

According to MS CEO, Windows 10 is no longer an operating system but has been transformed into a service. I assume this is another miracle of modern semantics, but it is Mr. Nadellas story and he is sticking to it. Personally, I will never install W10 in anything like its existing form on a PC that I seriously need to have working reliably for mission critical activities. That is just my personal opinion but the lack of stability to this OS and other abusive features just leaves me stone cold.

Reply | Quote

It is not meant to be an OS but a service. I think Mr Nadella could not be more clear about it.
It is suitable for a terminal maintained dynamically and connecting to Cloud services and less to be installed on a PC in a traditional way, unless in an Enterprise where it would be fully managed by professionals and in such a case it would be part of what some name “Private Cloud” if not of the Public Cloud.

Reply | Quote

Well thats good news for the “Home Folks” Well that being said I may just upgrade 😉 (just kidding way to late for that lol)

You got to stop splashing nearly a full screen Win10 settings page on my poor little Win7x86 machine it near gave me a Heart attack, I’ll have to reach for a Beer now to steady my nerves 🙂 (purely Medicinal you understand, now wheres that “Singha”?)

Reply | Quote

For me personally I’m uncomfortable with all these “builds.” I mean if they want to have Windows 10 be a service, then that’s fine, but I feel they should make one build and have it be the standard for at least 5 years and then release a new build of Windows 10 and have it be up-gradable when a new build does come out. But then I suppose that would be the same as just releasing an entirely new version of Windows every few years.
But if you have one build at a time then you can at least make sure it’s stable and that the updates for it are as stable as possible.

Reply | Quote

I wonder if it’s 35 days from patch release or 35 days from when you tick the setting to pause?
If it’s from when you tick the setting to pause, I then wonder if you can trick it by removing the pause and then pausing it again later, and it starts the 35 days all over again.

Reply | Quote

The ‘Pause Updates’ feature could easily be removed in a future roll-up/ update..without you knowing.

Nah, had enough of their BULL shifting, come January 2020:

Bye Bye Microsoft, hello Linux!
Goodbye Patchy mess, welcome to the Repo’s

Reply | Quote

I think sure that those options will not actually work for Home edition
if those options are reflection for the same group policies (available in ver 1607), then they are controlled by the kernel product policy licenses
meaning, it’s just like when you set registry policies for WU in Home, they are ignored nonethesless

i guess that’s what Dona ment when she stated it’s for Pro and up

Reply | Quote

According to Microsoft’s video “An overview of Windows as a service” (https://www.youtube.com/watch?v=MLc4-Suv0LU), for businesses, Current Branch can be considered a pilot release, and Current Branch for Business is for broad deployment and use. So Windows 10 Home users are using a pilot release apparently?

Reply | Quote

Yes the option to pause updates is there on the screen but has anyone been able to check whether it actually works?

Reply | Quote

Well, it’s about time. At least we humble Win 10 Home users will be able to defer things until such time as Woody gives us the nod.

🙂

Reply | Quote

I wonder if you can “resume”/”Pause” ever 35 days to keep it from updating? 🙂

Windows 10 to Include Privacy Changes Helping Microsoft Avoid Lawsuit

http://news.softpedia.com/news/windows-10-to-include-privacy-changes-helping-microsoft-avoid-lawsuit-511766.shtml

Reply | Quote

My article on the privacy settings has been delayed until Monday.

Not sure about the Pause setting.

Reply | Quote

No, and we won’t have a chance for a long time. The updating cycle for Insider Previews is not well defined.

Reply | Quote

Not only Home, but also all Pro users who aren’t waiting to manually upgrade to the CBB when it’s established.

Reply | Quote

Chokdee kap!

Reply | Quote

Thats a really good point @ThymeJ I was just thinking at the same moment. The old Windows system time or Bios time dodge. Has worked in the past for other stuff. M$ would be on to that surely or would they………..?

Sure would give folks a lot of flexibility if you could live with a Machine temporarily “Jet lagged”

Reply | Quote

It couldn’t possibly be a bug, Woody. Where did you hear that Windows 10 had any bugs?

(where did that sarcasm emoji go now???)

Reply | Quote

+1

Reply | Quote

… and Enterprise and Education if they aren’t waiting for CBB and upgrade at CB either individually or as part of the Enterprise policy.
LTSB when it gets released on the other hand, is at the CB level from very beginning. Think Windows 10 Enterprise LTSB 2016 or Windows Server 2016 (the server was delayed, but still released before the build went CBB).
The only difference for Home Edition users is that they should not have a choice and this is by design, while everyone else other than LTSB have a choice.

Reply | Quote

LTSB is a special build and should not be used for general purpose productivity tasks while the server is a different thing.
There is always the risk while using Windows 10 Enterprise LTSB instead of Windows 10 Enterprise that something can go wrong unexpectedly and there is no reasonable way to recover. For example LTSB is not supported on Surface and there will always be driver issues and some drivers may even be blocked in the same way like certain drivers for desktops are blocked on servers, for various reasons, commercial, but technical sometimes, i.e graphics drivers for desktops can cause BSOD on servers. There are licensing differences between the 2 versions too.
It is so easy to configure Enterprise to behave like LTSB and still be under supported scenarios.
It takes exactly 2 Group Policies: Allow Cortana – Disabled and Disable all apps from Windows Store – Disabled (the setting name is counter-intuitive, but this is the correct one, not Enabled).
There are few other policies related to the Cloud configuration, but they have a lot less impact than the 2 already mentioned and I would say that they are optional, although useful.

Reply | Quote

This build is above 1607 mentioned by abbodi86.
So there is still a chance…
I wouldn’t rely on the Home Edition though and I think the readers here have enough interest in what is going on behind the scenes to use only Pro and above.

Reply | Quote

The cloud is a must because they can’t wait to dig into user data to collect info. That’s the next stage when they run out of ways to spy on everything else.

Reply | Quote

Well, WU is shared across all editions

in Windows 10 ver 1607, some Enterprise features are available for Pro, but they do not work unless Enterprise license is activated
example:
https://social.technet.microsoft.com:443/Forums/office/en-US/c1b1d99f-ba29-41f7-af4c-e5ec2e5f8b69

Reply | Quote

HA!

Reply | Quote

I have run ltsb from the beggining. i game with it and have zero problems with it..no driver problems no crashes.it is the best os available..

Reply | Quote

That was an acknowledged bug which was fixed a month ago: http://serverfault.com/questions/821316/why-doesnt-the-nfs-client-work-in-windows-10-pro

Reply | Quote

It was not actually a bug, but an intended behavior for merging Enterprise license/features into Professional edition to allow in-place upgrade without reboot

they may have fixed it for NFS, but there are other features affected such as Device Lockdown, Device Guard, Network Connectivity Assistant, RemoteApp
i have not tested to see if they all are fixed

Reply | Quote

Well, any discussion about version 15xxx is certainly about beta (pre-release) software.

That being said I tend to agree that a continuous roll-out of software really isn’t appropriate for an operating system, there ARE plans you can get on that make it less like “continuous beta”…

There is, for example, the Current Branch for Business (CBB), where you don’t get the OS update until after it’s been used by millions of people for months.

-Noel

Reply | Quote

For what it’s worth, Softpedia reports (http://news.softpedia.com/news/windows-10-home-users-won-t-be-able-to-pause-updates-in-creators-update-511778.shtml):

“The latest Windows 10 Insider build aimed at users enrolled in the Fast ring comes with an option that makes it possible to pause updates for up to 35 days, but this feature will only be available for Windows 10 Professional, Education, and Enterprise.”

Reply | Quote

As far as I can see, it is 35 days from when you tick the setting. Note that when you remove the pause, Windows will first search for and install updates before you are allowed to pause again. You might be able to work around this by disabling your internet connection.

Reply | Quote

Or by using wushowhide.

35 days later, there will undoubtedly be a new update, so a35 day delay is basically a”skip this update”.I think.

Reply | Quote

Right. Bogan is repeating the official documentation.

Reply | Quote