SCCM – Deploying .NET Framework 4.6.2 Fails With Error 16389

Hello everyone,

In preparation for some upcoming application deployments that rely on the latest .NET Framework I did a test deployment to a small (50-ish) collection of Windows 8.1 x64 laptops.

My .NET 4.6.2 setup is fairly simple: it’s in SCCM as an application using the full executable and my full install looks like this:

NDP462-KB3151800-x86-x64-AllOS-ENU.exe /q /norestart

Almost immediately I had a failure and they kept rolling in, all failing with a 16389.

Luckily, the fix was fairly simple…

After a quick look online I went into my application and in the ‘Program’ tab I had to click to enable the “Run installation and uninstall as 32-bit process on 64-bit clients.”.  D’oh!

There it is:

net4.6.2

Once that was clicked and redistributed out to the distribution points (just to be safe) the angry red failures have all disappeared!

7 thoughts on “SCCM – Deploying .NET Framework 4.6.2 Fails With Error 16389

  1. Vasile Jichin

    Technically this has no sense, you have a bundle that contains both 32bit and 64bit .NET, you run it on a 64-bit system. What does SCCM by default is to run a 64-bit installer with the 64-bit paths and a 32-bit installer with the 32-bit paths. So once again, installing a 64-bit app in our case on a 64-bit system should not have any effect if that check is on? …

    Like

    Reply
    1. nbb359 Post author

      The only thing that makes sense (well no, it still doesn’t make sense) is that there is either a) a funky setup process within the installer or b) the installer runs as 32-bit and just puts the bits in the 64-bit places if it can do so or some combination of both. It was still the same as of 4.7.1 if I remember correctly when last I looked at it.

      Like

      Reply
      1. Vasile Jichin

        Which leads to the conclusion that the installer is badly coded, you cannot have cross-references of different architectures, but who knows, maybe the versatility of this x86&x64 makes it so “special”. Thanks for the tips

        Like

  2. Pingback: Error 16389 for .Net Framework 4.6.2 as SCCM Application | Application Packaging and Virtualisation Specialists

  3. Pingback: Forcing an app into 32-bit mode - How to Code .NET

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s