locked
Cant start my .NET 2.0 application without intervention of feature activation dialog and afterwards windows update necessity leading to BSOD

    Question

  • Hi,

    the title of the thread says it all: I want to start one of my applications targetting the 2.0 .NET Runtime, but the execution is intercepted by the Feature Activation Dialog asking for 3.51 .NET activation. You cant skip this and are forced to continue, after some while of preperation, the dialog tells me that i have to connect to windows update to continue, otherwise the procedure wont finish. After some time of "blind-nowhere" Updating (i know its a DevPrev Windows, so there will be no real updates!), i get this wonderful BSOD telling me that we have a Windows Kernel level issue of type KERNEL_STACK_INAPGE_ERROR:

    (Screenshot)

    http://www.pro-it-education.de/staff/all/W8_DP_BS_KSIE.jpg

    So my question: How do i manage to run my .NET 2.0 application on that system, if, possible without the need of running windows update, or feature activation of .NET 3.51 (2.0 or 3.0 should be system standard at all!). There should be at least 2.0 or 3.0 available  as it was on Vista and 7 by design.

    Thanks in advance,...

    K.
    ------------------------- Beste Grüsse / Best regards / Votre bien devoue Kerem Gümrükcü http://entwicklung.junetz.de ------------------------- "This reply is provided as is, without warranty express or implied."
    • Edited by Kerem_Gümrükcü Thursday, September 15, 2011 10:20 AM
    • Moved by BillFillMicrosoft employee Friday, September 16, 2011 11:36 PM Looks like a Dev question .... doesn't fit well in General OS (From:Windows Developer Preview: General OS questions )
    Thursday, September 15, 2011 10:18 AM

All replies

  • Hey there,

    Do you mind sharing the name of the application you are trying to run and encountering this error?

    In the Desktop UI, have you tried to run the app in a compatibility mode? Did that work?

    Regards,

    Bobby

    Friday, September 16, 2011 6:20 AM
  • Hey there,

    Do you mind sharing the name of the application you are trying to run and encountering this error?

    In the Desktop UI, have you tried to run the app in a compatibility mode? Did that work?

    Regards,

    Bobby

    Hi Bobby,

    its an internal application in our company but it does not make any difference whether using this app or some ordinary most simple entry one (link provided to sample with code later) dotnet 2.0 target assembly exe. Its always the same, even using compatibility mode has no option for that. You even cant start it in comp. mode since the system always requests the installation of the 3.51 dotnet redist. before doing anything and then, while doing that "from-nowhere" update goes BSDO. Here is the most simple main() c# coded net assembly,...and even that wont work and how should it work, because the systems pe loader detects it as an .NET assembly and falsely detects dependencies to 3.51 (there are none!), then before doing anything needs to install the Net Framework before it can do anything. So, whats wrong here? In fact the OS is a dev prev so there isnt a lot to expect, but the most simple things do not work,...thats pretty sad,... :-(

    http://www.pro-it-education.de/staff/all/EntryPointOnlyDotNET20Assembly.zip

    cheers

    K.

    ------------------------- Beste Grüsse / Best regards / Votre bien devoue Kerem Gümrükcü http://entwicklung.junetz.de ------------------------- "This reply is provided as is, without warranty express or implied."
    Friday, September 16, 2011 9:52 AM
  • Hello,

    so I tried this on two different machines but I don't see the BSOD.  While waiting for windows update to finish, the machine is installing .Net 3.5.1 on the system which sits on top of .Net 2.0.  After you reboot into the system from the BSOD, is the directory windows\microsoft.net\framework\v2.0.50727 populated with assemblies? 

    If you go to Control Panel | more Settings | Programs | Turn Windows features on or off, click on Microsoft .NET Framework 3.5.1, unclick the two child nodes underneath - Windows Communication Foundation HTTP Activation and Windows Communication Foundation non-http Activation.  click on OK.  Do you get the BSOD in that scenario?

    I understand where you are coming from in this post -

    - lobbying for .NET 3.5/2.0 to come preinstalled on a standard install of Windows.

    - we don't get the BSOD during a windows update.

    Let's see if the BSOD is related to Windows trying to install the feature first.

    much appreciated,

    Mike Wong

    Microsoft Developer Support

    Monday, September 19, 2011 9:54 PM
    Moderator