Shulou(Shulou.com)06/03 Report--

Users remain skeptical of client-device patch updates because they fear their computers will suddenly reboot themselves without permission and lose data. Although, you can defer a restart after an update and schedule it for a selected time, depending on the update Windows may still restart your computer after a while without your permission, and it will not function properly without a restart.

Usually we need to do preparatory work before installing patch updates. First, make sure our data is backed up in multiple locations, so if the system crashes, I can rebuild my computer and recover data from backups. I backup my data in two locations on the network, and I backup it in the cloud. Cloud backups run silently in the background and don't interfere with my daily tasks. Sometimes I accidentally delete files or overwrite data, and sometimes I have to go to the cloud to grab the files I want.

Below we describe using Group Policy to prevent Windows 10 from restarting without my permission after installing updates.

You can configure two types of Group Policy. In a domain environment, you can use Active Directory to configure settings that may affect multiple computers on your network, Windows workstations or Windows servers. If you don't have a domain environment for Active Directory, then even if you only have one computer, a workgroup environment. In other words, all Windows computers are part of a domain or workgroup. If you are in a workgroup environment, such as a small network of 10 or fewer computers, or if you use a desktop or laptop at home, you can use the local Group Policy Editor to get the same results.

Configure Group Policy on a Domain

Log in to one of your domain controllers and follow this procedure.

1. Start the Group Policy Management Console (GPMC) on the Domain Controller and go to GPMC - > Forest: Contoso.com- > Domains- > Contoso.com - > Group Policy Objects- > Default Domain Policy. You can use any other group policy. If you plan to apply a policy to the default domain policy, I recommend that you create another policy and call it the Contoso default domain policy, and then apply this policy to the Contoso.com domain. You simply click and drag the new policy you create to Contoso.com to link it. You can also selectively create and apply policies to specific computers in a department or departments without applying them to the entire domain.

2. Edit Contoso default domain policy.

3. Go to Computer Configuration- > Administrative Templates- > Windows Components- > Windows Update.

4. Double-click "No automatic restart, login user to schedule automatic update installation."

5. Select the Enabled radio button and click OK to apply the setting.

6. Verify that the state of the setting has never been configured to enable, and then close the Group Policy Management Editor.

7. You can either run gpupdate / force on each machine to implement the change immediately, which is impractical in most cases; restart all machines, which is also undesirable in most cases; or wait for the next automatic update of machine settings on the machine, which is a reasonable option for such non-emergency modifications. You can always run gpupdate / force from a command prompt on any computer using administrative credentials, which refreshes computer policies and user policies on the local computer. There is no harm in running gpupdate; running it on all computers is just too much work.

Description:

After selecting the Extensions tab in the right pane of the Group Policy Management Editor, as shown in the screenshot above, you can read the description of each policy setting. This policy specifies that automatic updates will not automatically restart the computer if scheduled installations are to complete. It waits for the logged in user to restart the computer.

"If the status is set to Enabled, automatic updates will not automatically restart the computer during the scheduled installation when the user logs on to the computer. Instead, automatic updates notify the user to restart the computer. "

For this policy, the computer must be restarted for the update to take effect. If the status is set to Disabled or the default is Not Configured, Automatic Update lets the user know that the computer will automatically restart in 5 minutes to complete the installation.

Note: This policy applies only if automatic updates are configured to perform scheduled update installations. If you disable the Configure Automatic Updates policy, this policy has no effect.

Configure Group Policy on your local computer

If you do not want to implement this change on multiple computers in your domain, you can configure this policy locally on your computer using the local Group Policy Editor (gpedit.msc). You can use the Local Group Policy Editor on any Windows computer at any time. However, depending on how the domain administrator configures Group Policy in Active Directory, local policies may be superseded by domain policies.

1. On Windows computers, type gpedit.msc in the Search box, and then press Enter.

2. Go to Computer Configuration- > Administrative Templates- > Windows Components- > Windows Update.

3. Double-click "no automatic restart, login user to schedule automatic update installation." "and select Enable.

4. Click OK and close the Local Group Policy Editor.

5. Run a command prompt with administrative credentials, type gpupdate / force, and press Enter. This refreshes the machine policy and user policy on the local computer. You can also log out and log back in, or restart your computer to apply the changes, but in general you only need to do this if the applied policy doesn't work.

6. When prompted to restart your computer, you can click Pause to remind you again later, choose when you want to restart your computer, or restart your computer if you can.

Note: When you use GPMC to configure policy on a domain, it does not modify the local Group Policy Editor. It simply implements Group Policy through Active Directory on the domain controller. If a policy that conflicts with a domain policy is configured on the local computer, the domain policy is enforced. Policy application order:

Local- > Site- > Domain- > Organizational Unit

Local Group Policy settings on computers are applied first, policies configured at the Active Directory site level take effect, policies are configured at the domain level, and policies at the organizational unit level are applied last. This gives enterprise domain administrators full control over enforcing corporate policies and prevents employees from circumventing policies applied by the organization at the domain level.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.