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

In this issue, the editor will bring you about how to solve the problem that commercial computers encounter Windows system updates must be restarted to take effect. The article is rich in content and analyzes and describes for you from a professional point of view. I hope you can get something after reading this article.

The author saw a post on the Microsoft News Group a few days ago asking how to make customer-oriented commercial computers install certain system updates that must be rebooted without popping up a dialog box confirming the restart, so as not to let this dialog box interfere with the normal use of customers. Although the author has provided some suggestions, but because the computer described by the questioner is too "commercial", it has not been solved perfectly in the end. It seems an irreconcilable contradiction that some system updates must be restarted and commercial computers cannot be restarted while they are working.

Why do some Windows system updates have to be rebooted to take effect at installation? This is mainly due to the fact that the system files that need to be upgraded are currently being used by the operating system, and the lack of corresponding system files will immediately cause the crash of Windows, so we have to close Windows and restart, and complete the upgrade of the corresponding system files in the process of restart. For example, MS09-025 (KB968537) released this month (June 2009) is one such update, which involves an upgrade of Windows kernel files that must be restarted. On the contrary, other updates that need to upgrade system files that may not be in use may not need to be restarted during installation, such as MS09-022 (KB961501) released this month, if we do not currently enable the Windows background printing service, we may not need to restart when installing this update.

It is precisely because some updates must be restarted when they are installed, in order to prevent possible data loss caused by the restart, the update will pop up a confirmation dialog box to remind the user before restarting. Once the dialog box pops up, it is possible to interfere with applications in the foreground of commercial computers, leaving customers who are using foreground applications (such as those who are operating bank ATM machines) or non-computer professionals (such as workers of the age of aunts and aunts who don't know much about computers) at a loss what to do. In order to avoid such trouble, we should try our best to avoid commercial computers popping up the restart confirmation dialog box at work. This can be handled with reference to the following situations:

1. Install the update locally:

If we install the update by manually downloading the installation file from the Microsoft website and saving it locally (.MSU or .exe file), and then performing the installation manually, we can add two parameters-QUIET-NORESTART on the command line. -QUIET means to perform the installation silently without human intervention;-NORESTART means not to restart if the update needs to be restarted. This allows you to install the update quietly and restart it manually after working hours. Note that the NORESTART parameter requires the combination of the-QUIET parameter to take effect, and it doesn't make sense to use it alone.

This method is more suitable for one or two public computers in the office. For example, this morning I found that Microsoft had issued a June security bulletin and manually downloaded the updated installation files. You can install them first with the method of-QUIET-NORESTART, but do not restart them. During the day, the work of this computer will not be affected by the restart. By the time the computer is turned off at the end of the day and rebooted tomorrow morning, the updates that need to be rebooted will have been installed.

two。 Install the update as WUAU or WSUS:

After all, the way to install locally is a bit cumbersome, so many people choose to turn on WUAU local automatic updates. For enterprises with a large number of computers, deploying WSUS is also a wise choice. However, installing updates in WUAU or WSUS cannot apply the-QUIET-NORESTART parameter, which is specific to local installation, and there is currently no way to extend WUAU or WSUS. If we have started the installation of updates that need to be restarted through WUAU or WSUS, then this updated restart dialog will not be avoided. Although there is a "scheduled automatic update does not restart automatically after installation" in the group policy, it cannot completely block the appearance of the dialog box. The only difference is that when this policy is enabled, the user is asked whether to restart immediately, and when this policy is disabled, the user is notified to restart automatically after five minutes. Both types of dialogs will interfere with the foreground programs of commercial computers.

Therefore, if we do not intend to cause any interference to the foreground programs of commercial computers, we can only ask WUAU or WSUS not to start the installation of updates for the time being, but to download the updates and postpone the installation. We can set "configure automatic updates" in "computer configuration"-"Administrative templates"-"Windows components"-"Windows Update" in Group Policy, and then select the fourth item "4. Automatic download and schedule installation" and set a scheduled time outside working hours. In this way, during the working period, WUAU or WSUS will only get updates in the background, but suspend the installation. As long as the installation is not performed, there will be no prompt at the front desk of the commercial computer; wait until the non-working hours, and then install the update and restart according to the planned time.

3. Non-rest 7 × 24-hour commercial computer:

Whether it is a local installation or WUAU or WSUS, the two methods mentioned above simply delay the restart of the update to non-working hours. But we know that there are many commercial computers that have no rest 24 hours a day, and they may only have a precious chance to restart once a day, every week, or even once a month. The problem that the author encountered in the newsgroup was the application of WSUS's 7 × 24-hour bank ATM machines. These ATM machines can only have a chance to restart when there are few users at three or four o'clock every morning. But even if "scheduled automatic updates do not restart automatically after installation" is set to enable, even if the scheduled time is 3: 04:00 in the morning, the ATM will still encounter problems.

According to this man, the touchscreen program of the ATM machine is full-screen and in the foreground by default, which can determine whether the user has taken his bank card. If there is still a card in the ATM machine, the touchscreen program can prevent the ordinary ATM machine from shutting down, but it cannot prevent the update restart dialog box from seizing the foreground, and WSUS is unable to judge whether the user has taken the card, so it is easy to cause problems. For example, suppose a night owl user who does not sleep in the middle of the night comes to withdraw his money at three or four o'clock in the morning, and when the bank card is not removed, WSUS plans to restart, and the touch screen program of the ATM machine will be forced to go to the background after the restart dialog box appears, at this time the user can no longer touch the operation, but can only choose to make the update restart. However, after restarting, the re-run ATM touchscreen program will not be able to spit cards. It is forbidden to spit cards in order to prevent others from stealing cards because of the bank's regulations that users may leave the scene to ask for help when they restart. At this time, the night owl user could say that the sky should not be answered and the earth would not work. Even if he went to the bank staff for help, he would have to wait several hours until the bank went to work at dawn.

After reading this man's description, the author feels that both the update program of the system and the touch screen program of the ATM machine need to be improved. If the system update program can not pop up to seize the foreground dialog box, but only prompt in the notification area of the taskbar, it will not cause the failure of the ATM touchscreen program; if the ATM touchscreen program can always be forced to display in the foreground, all pop-up dialogs will be blocked in the background, just like the Windows task manager, it can also prevent itself from being robbed of the foreground display by the restart dialog box. No matter which side can "take a modest step" or "be tough", this problem can be solved. In short, there seems to be no good solution to this problem at present, and we can only hope that the system update program or ATM touchscreen program will be improved.

This is how to solve the problem that commercial computers encounter Windows system updates must be restarted to take effect. If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

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.