What it did, exactly?

Well, it just monitored my Internet bandwidth (current speeds of download/upload).

These were the times of good ol’ dial-up connections (33.6 kbps or, when you were lucky, 48-56 kbps).

Now these times are long gone, and speed is measured in Mbps, not in kbps… :-)

But DU Meter is still there, and Hagel Tech even released a brand-new version – 4.0:)

You can download it here: http://www.dumeter.com/download.php

It’s a trial, which will work for 30 days; after that, you can either stop using it, or buy a single license for USD 24.95.

Still, you should be aware, that a similar app exists now, and it is called Net Meter (current version is 1.1).

It does exactly the same things as DU Meter, but it’s freeware (you can make a small donation, though, if you like the program).

I tested both apps. Net Meter, to be frank, simply copied most of DU Meter’s interface look & feel (which is a good thing, if you are accustomed to DU Meter, but do not want to pay 25 dollars to buy it), and, apart from that, I do not see any major differences between them.

Which one to use, you may decide for yourself; still, it’s nice to know you have more than one option! :-)

Windows XP updates automatically, and then a small box appears, which gives you two choices:

1. Restart the computer! (now)
2. Restart the computer! (later)

The problem is, even if you choose the ‘later’ option, the same annoying dialog box will pop-up after 10 minutes or so and you’ll have to dismiss it again, then again, then again… Finally, it will inform you, that the computer will be automatically restarted in 5 minutes, no matter what you do currently — the only choice you have at this moment is to postpone the restart a little, but the box will come again and again… And if you’re in the middle of something, and cannot restart right now, then what?

Luckily, there’s a solution, which I’ve found by accident, while browsing the Internet with no specific goal (you may read about this solution in a lot of places, actually). In short, your options are the following:

Option One

Stop the Automatic Update Service for the moment.

To do so, open the ‘run’ dialog box (shortcut: Windows key + R), type ‘cmd’ (without the quotes, of course) in it and hit ENTER. The command line will open.

Then use the following command to stop the service:

net stop wuauserv

Alternatively, you may also use:

net stop "automatic updates"

Or:

sc stop wuauserv

All of these do one and same thing: they stop the Automatic Update Service and with it, the annoying box, which prompts continuously you to restart the computer.

Then you may restart the computer at whatever time you like:-)

Note: The Automatic Update Service will be automatically started at the next Windows reboot, so don’t worry, you won’t disable the service itself!

Now, to the next option:

Option Two

You may disable this dialog box, prompting you to restart the computer after the Windows updates are applied, for good:)

How?

Again, open the ‘run’ dialog box, and type in it ‘gpedit.msc’, then hit ENTER. This will open the Group Policy editor.

Locate in it:

Local Computer Policy → Computer Configuration → Administrative Templates → Windows Components → Windows Update

There are two options there which will affect achieve the effect you’re after.

The first one is: No auto-restart for schedule Automatic Updates installations

Right-click it, select ‘Properties’, and configure it.

The second one is: Re-prompt for restart with scheduled installations

Right-click it, and set the time interval to something very long, like 720 minutes (12 hours).

Note: The maximum number of minutes you can set up there is 1440 minutes, or 24 hours, but this should be enough.

That’s it. No more annoying boxes popping up everywhere and urging you to restart NOW:)

What next?

Finally, let me quote Tim Rains on what might be the issues when disabling this auto-restart dialog box:

IMPORTANT: If you choose to configure your system not to reboot when a security update which requires a reboot is installed, you are taking a huge risk. The fixed code is not actually loaded (in memory) by the system until after the reboot. i.e. the old, vulnerable code is still running until a reboot is completed. If you do not reboot the system for whatever reason (you didn’t realize a security update was automatically installed, you want to wait for a regular maintenance window, you forget, you were on vacation, etc.) your system will still be vulnerable. You also risk system stability by delaying a required reboot. When some files that are in use are replaced but not loaded, and other files that are not in use are replaced, you can get into a mixed binary situation. Depending on the binary, there may be conflicts that cause system instability.

Also, here should be noted that if you have the Automatic Windows Update service disabled by default (System Properties → Automatic Updates → Turn Off Automatic Updates) and do your updates manually (via Microsoft Update or Windows Update), then this dialog box won’t bug at all you after updates are installed, because you have decided to install them manually.

Other interesting resource for you might be this one:

http://www.codinghorror.com/blog/archives/000294.html

There are a lot of insightful comments below the main article — you may find in them, for example, what to do if you’re running a copy of Windows XP Home Edition, which doesn’t have a Group Policy Editor; what are the differences between the No auto-restart for schedule Automatic Updates installations and Re-prompt for restart with scheduled installations and how to set them up in the best possible way, etc.

I’ve created this article more as a note to myself, so I can reference to it later, when needed:)