Skip to main content

You have Moved an Icon on Your Desktop

Your computer must be restarted for the change to take effect.

We used to joke about Windows 95 and it’s ridiculous reboot requirements.  The line we used was:

“You have moved an icon on your desktop. Windows must be restarted for the change to take effect.”

Those were not the days, and I thought that they were pretty much over.

Apparently not:


I can’t think of any circumstances where a reboot should be necessary to complete the installation of application software. That was last century. I’m OK with reboots for things like kernel updates, firmware updates, and perhaps even driver updates.

But a browser?

It’s possible that the reboot is being forced by non-Mozilla browser add ons – I don’t have any way of knowing. But if an add on to an application can force the application to force the operating system to reboot, then the application and OS design are both defective.


  1. You could say the same about browser extensions - why do we need to restart Firefox after extensions are installed?

    And why does my copy of Firefox lose my extensions settings whenever it's updated - it's a PITA!

  2. I get similarly frustrated with Windows and restarts.
    The hosting company I work for started offering a new managed backup solution which I've had only peripheral involvement in.
    Orders started coming in and I merrily set about doing installs only to discover that for the Windows agent to work I had to reboot their server. Customers always love it when you have to reboot their servers. In my experience, often times when Windows says you need to reboot you don't so I did my best to bypass it but even the Backup software's Windows service wouldn't start and without logging anything helpful in Event Manager, so it had to be rebooted.

    I'm so glad my role focusses on *nix based stuff and we have a dedicated Windows server guy. I think I'd go prematurely grey if I had to keep working on windows boxes.


Post a Comment

Popular posts from this blog

Cargo Cult System Administration

“imitate the superficial exterior of a process or system without having any understanding of the underlying substance” --Wikipedia During and after WWII, some native south pacific islanders erroneously associated the presence of war related technology with the delivery of highly desirable cargo. When the war ended and the cargo stopped showing up, they built crude facsimiles of runways, control towers, and airplanes in the belief that the presence of war technology caused the delivery of desirable cargo. From our point of view, it looks pretty amusing to see people build fake airplanes, runways and control towers  and wait for cargo to fall from the sky.The question is, how amusing are we?We have cargo cult science[1], cargo cult management[2], cargo cult programming[3], how about cargo cult system management?Here’s some common system administration failures that might be ‘cargo cult’:Failing to understand the difference between necessary and sufficient. A daily backup is necessary, b…

Ad-Hoc Verses Structured System Management

Structured system management is a concept that covers the fundamentals of building, securing, deploying, monitoring, logging, alerting, and documenting networks, servers and applications. Structured system management implies that you have those fundamentals in place, you execute them consistently, and you know all cases where you are inconsistent. The converse of structured system management is what I call ad hoc system management, where every system has it own plan, undocumented and inconsistent, and you don't know how inconsistent they are, because you've never looked.

In previous posts (here and here) I implied that structured system management was an integral part of improving system availability. Having inherited several platforms that had, at best, ad hoc system management, and having moved the platforms to something resembling structured system management, I've concluded that implementing basic structure around system management will be the best and fastest path to …

The Cloud – Provider Failure Modes

In The Cloud - Outsourcing Moved up the Stack[1] I compared the outsourcing that we do routinely (wide area networks) with the outsourcing of the higher layers of the application stack (processor, memory, storage). Conceptually they are similar:
In both cases you’ve entrusted your bits to someone else, you’ve shared physical and logical resources with others, you’ve disassociated physical devices (circuits or servers) from logical devices (virtual circuits, virtual severs), and in exchange for what is hopefully better, faster, cheaper service, you give up visibility, manageability and control to a provider. There are differences though. In the case of networking, your cloud provider is only entrusted with your bits for the time it takes for those bits to cross the providers network, and the loss of a few bits is not catastrophic. For providers of higher layer services, the bits are entrusted to the provider for the life of the bits, and the loss of a few bits is a major problem. The…