How to avoid OS reboot prompt when installing the .NET Framework 3.5 on Windows Vista

re: How to avoid OS reboot prompt when installing the .NET Framework 3.5 on Windows Vista

Aaron Stebner — Tue, 06 Nov 2012 15:52:19 GMT

Hi Another puzzled tech - It is possible that the .NET Framework 4 will require a reboot in the way described in this blog post. It is not guaranteed to happen 100% of the time, so you shouldn't assume that it will certainly show up. However, your installation process should include logic to check the return code from the .NET Framework setup process and prompt the user to reboot if the return code is 3010.

re: How to avoid OS reboot prompt when installing the .NET Framework 3.5 on Windows Vista

Another puzzled tech — Tue, 06 Nov 2012 14:21:40 GMT

Hello all,

Does anyone know if I may run into this same sort of thing installing .NET 4.0 full?

Should I presume that this will certainly show up if the 4.0 is installed unto a machine that has not even the 3.5 version?

re: How to avoid OS reboot prompt when installing the .NET Framework 3.5 on Windows Vista

test — Mon, 21 Nov 2011 11:41:32 GMT

error when installing vs2008 on vista

re: How to avoid OS reboot prompt when installing the .NET Framework 3.5 on Windows Vista

Marshall — Wed, 22 Oct 2008 05:56:29 GMT

My setup application has to pre-install the .NET Framework 3.5 and ran into the same issue that the reboot prompt dialog shows up.

Using the IAutomaticUpdates::Pause and IAutomaticUpdates::Resume, the dialog disappears but even worse, it will reboot while my setup application is still running without any warning.

I called the IAutomaticUpdates::Pause at the first beginning of the setup application and called the IAutomaticUpdates::Resume at the end of the setup application. The rebooting happens before calling the IAutomaticUpdates::Resume.

Can anyone tell me how to work arround this issue? It has been a testing blocker right now.

Thanks!

re: How to avoid OS reboot prompt when installing the .NET Framework 3.5 on Windows Vista

Aaron Stebner — Mon, 21 Jan 2008 21:34:11 GMT

Hi Jsn_segal - I discussed this scenario with a few folks who work on the WUA APIs and Automatic Updates here at Microsoft. They indicated that there is not a way to detect that an Automatic Updates download is in progress, but that Automatic Updates will not proceed to the installation phase for an update if Pause was called.

re: How to avoid OS reboot prompt when installing the .NET Framework 3.5 on Windows Vista

Aaron Stebner — Tue, 15 Jan 2008 03:38:35 GMT

Hi Jsn_segal - I had expected that the Pause method would prevent Automatic Updates from proceeding to install an update after it got done downloading in this type of scenario. I will try to ask around and see if I can find someone who works with the WUA APIs more closely to see if there are any options for handling that scenario.

Problem with the Pause/Resume Workaround

jsn_segal — Tue, 15 Jan 2008 01:39:35 GMT

I've been working on a simple application to implement the WUA Update/Resume workaround for my installer. Here's how it works:

1. Check for pending reboots. If A reboot is required, alert the user and quit.

2. Check for WUA installations in progress. If one is in progress, alert the user and quit.

3. Pause the WUA

I'm not currently bothering to resume, since this should happen in 8 hours anyway (or the next time the user reboots).

The problem is that, while the IUpdateInstaller interface's IsBusy property allows me to make sure no WUA installations are running, I don't see any way to determine whether or not a "download and immediately install" cycle is currently in its download phase. This means that if an update is being downloaded when my installer starts, the WUA may begin installing it and interrupt my installer despite all the precautions.

Is there a way to detect WUA downloads in progress (other than the ones you initiate) or prevent them from installing after the download completes? (I hoped that using Pause would do the latter, but it doesn't seem to.)

Be careful when installing Visual Studio 2008 RTM on your Vista. « Varely’s Weblog

Fri, 21 Dec 2007 16:44:06 GMT

PingBack from http://varely.wordpress.com/2007/12/21/be-careful-when-installing-visual-studio-2008-rtm-on-your-vista/

re: How to avoid OS reboot prompt when installing the .NET Framework 3.5 on Windows Vista

Aaron Stebner — Mon, 17 Dec 2007 00:58:23 GMT

Hi Peterchen - I definitely understand the possible user confusion caused by this issue. The worst part is that this issue can affect any application that installs the .NET Framework 3.5, not just developer tools like Visual Studio. I've communicated all of the feedback collected on this blog post to the .NET Framework setup team, but there's not a lot more I can do in the meantime. I'm going to try to work with them to create some sample code to implement the WU pause/resume APIs described above.

Also, I've experienced this issue on a couple of systems since the time that I posted my original comments about this issue, and it is worse then I initially anticipated because the time it takes to install 2.0 SP1, 3.0 SP1 and 3.5 on Windows Vista RTM can be really long. That makes it more likely that folks will notice the reboot prompt from Windows Update even if they're not actively watching their systems during installation of 3.5. The main piece of good news is that this issue won't affect systems that have Vista SP1, but of course that won't be available for a few more months, plus it doesn't provide a solution for applications that want to only require Vista RTM.

re: How to avoid OS reboot prompt when installing the .NET Framework 3.5 on Windows Vista

peterchen! — Sun, 16 Dec 2007 03:57:45 GMT

Aaron,

with all respect (and kudos for discussing this), I think your assesment is removed from end user reality.

The typical end user cannot tell apart "Funny Photos Setup" from "Windows Update". He's installing his new toy, a message pops up to "reboot to finish installing", and if he does, he's probably screwed.

The typical support call is "Your software broke my system", and you will be lucky to figure out that it happened during installation.

It's a hard job to train end users to actually reboot their system when a setup or Windows Update says "reboot". That impulse might actually a few hapless helpdesk souls, but next time our user will say "some computer guy told me not to reboot when this comes up". Some 3rd party vendors will work around by telling their users to deactivate Windows Update.

Microsoft expects one billion Windows computers next year. This is a component that will be redistributed by aspiring coders that wanted to "creating fun, cool projects that run on Windows" (quote MS web site), not fix installers.

This is the setup for a system update getting hairy with a system component that is core to security and stability.

I know these things aren't easy to get right. But if Microsoft doesn't think it's important, why should "we" - 3rd party developers?

I understand that your position is no official Microsoft statement, and I assume the bug is not your fault. I just wish you understand that there are more than just the technical issues.