A customer was writing a debugging tool and wanted to know in their installer which processor architectures are supported by the current system, both the native architecture as well as anything supported by emulation. That way, the tool could install the versions that apply to those architectures.<\/p>\n
Okay, getting the native architecture is easy. You can call Getting the emulated ones is a little trickier. Back in the old days, you just hard-coded some knowledge. “Well, Windows on x86-64 can emulate x86-32. And Windows on AArch64 can emulate x86-32 as well as T32.” But that broke down with the introduction of HoloLens 2, which is natively AArch64 and omits the x86-32 emulation, and then broke down further with the introduction of x86-64 emulation on native AArch64 systems.<\/p>\n To find out whether a particular architecture is supported in emulation, you can pass it to There is no way to get a list of all the architectures supported by emulation, primarily because there’s no real use for it. I mean, suppose you learn that Windows now supports architecture number 31415. You have no idea what that number means, because it’s not on your list of known architectures. Even if you somehow figured out that 31415 is Bonus chatter<\/b>: Sometimes, the kernel folks get a little cute when picking the ID numbers for new architectures. Here are the ones I was able to guess at:<\/p>\n Fortunately, there’s a special function for that, or at least for enough of that to serve your needs.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[25],"class_list":["post-106239","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":" Fortunately, there’s a special function for that, or at least for enough of that to serve your needs.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/106239","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=106239"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/106239\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=106239"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=106239"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=106239"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Get\u00adNative\u00adSystem\u00adInfo<\/code> to find out what the native system architecture is.<\/p>\nIs\u00adWow64\u00adGuest\u00adMachine\u00adSupported<\/code> and see what the answer is. Repeat for each architecture you are curious about.<\/p>\nIMAGE_\n\n
\n Architecture<\/th>\n Value (hex)<\/th>\n Proposed explanation<\/th>\n<\/tr>\n \n CEF<\/td>\n 0x0CEF<\/code><\/td>\nHex digits spell out name<\/td>\n<\/tr>\n \n CEE<\/td>\n 0xC0EE<\/code><\/td>\nWhy not 0x0CEE<\/code>?<\/td>\n<\/tr>\n\n EBC<\/td>\n 0x0EBC<\/code><\/td>\nHex digits spell out name<\/td>\n<\/tr>\n \n AMD64<\/td>\n 0x8664<\/code><\/td>\nAlso known as x86<\/u>–64<\/u><\/td>\n<\/tr>\n \n ARM64<\/td>\n 0xAA64<\/code><\/td>\nAlso known as AA<\/u>rch64<\/u><\/td>\n<\/tr>\n \n MIPS16<\/td>\n 0x0266<\/code><\/td>\nThere’s clearly something going on here
\nbut I don’t know what<\/td>\n<\/tr>\n\n MIPSFPU<\/td>\n 0x0366<\/code><\/td>\n<\/tr>\n\n MIPSFPU16<\/td>\n 0x0466<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"