Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8328871
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T01:34:47+00:00 2026-06-09T01:34:47+00:00

TLDR: When installing .NET on a 64-bit OS, are the 32-bit components always present?

  • 0

TLDR: When installing .NET on a 64-bit OS, are the 32-bit components always present?

I used to have my app (IronScheme) compiled entirely as AnyCPU. While this works great for all platforms, the 64-bit JIT compiler just seems too slow for my liking (about 550% slower startup and about 25% slower in general). The startup slowness can be solved by NGEN’ng my assemblies and does in fact improve startup time another odd 500% when done so. This is gives about a 2600% improvement on startup time (3700ms vs 140ms) on 64-bit. When both 32-bit and 64-bit are NGEN’d, the startup times are the same, but 32-bit still performs better at runtime.

Now given in most cases 64-bit is not needed at all, I think targeting x86 in the executable would just be the best general solution (all the other assemblies are targeting AnyCPU, but from what I can see, the executable determines where it goes). So the idea is to to have 2 startup executables, one targeting x86, the other x64 (or amd64 as MS calls it).

When installing on a 32-bit OS, I can be sure no 64-bit components are present. But what about the opposite case? Does the .NET installer install both 32-bit and 64-bit components? This is important as NGEN’ng a non-AnyCPU assembly will fail if the target does not match the runtime.

Example:

“Error compiling IronScheme.Console.exe: This version of is not compatible with the version of Windows you’re running.”

Also note that my application is built by default for .NET 2 and in VS2008, so the new AnyCPU (32-bit preferred) option (in VS2012/.NET 4.5) is not an option for me at this time.

PS: Sorry, if this has been asked before. I have no idea how to search for this specific issue, and my Google fu failed me too.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T01:34:48+00:00Added an answer on June 9, 2026 at 1:34 am

    are the 32-bit components always present on a 64-bit OS?

    No. But the case that it isn’t installed is somewhat rare. Windows Server Core 2008 R2 (and presumably Core 2012) support WOW64 as a separate, installable, and removable component – including the .NET bits. Take a look here for a little more information.

    In order to install the WOW64 components for Server Core 2008 R2 this needs to be run:

    Start /w ocsetup NetFx3-ServerCore-WOW64

    Server Core is the only case I have been able to find where the x64 components may be available, but the x86 ones may not be. If you are not targeting or supporting Server Core, then I believe it is safe to assume the x86 bits will be there along side with the x64 bits.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

TLDR I have a function that runs on the end of a pan in
TLDR : I have an Openlayers map with a layer called 'track' I want
TLDR: Does anyone have experience of both protovis & D3.js to illuminate the differences
tldr; When I run a rake task in a test app which uses an
(TLDR? Skip to the last couple of paragraphs for the questions...) I have a
TLDR: How do I force a rails app to use the correct ruby interpreter?
I have this code: filename = tkFileDialog.askopenfilename(initialdir=lists/custom/, filetypes=((Word list, *.tldr), (All files, *.*))) If
tldr; How to mark a JScript.NET dll as safe for scripting? Consider this JScript.NET
TLDR; skip to the bottom paragraph for the main question. I'll try to keep
TLDR: What are the pros/cons of using an in-memory database vs locks and concurrent

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.