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 3982606
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T05:32:52+00:00 2026-05-20T05:32:52+00:00

The following code works in Windows 7 x86, but not x64. What’s the difference

  • 0

The following code works in Windows 7 x86, but not x64. What’s the difference and how do I go about setting this key? It also works when I install it on Windows XP having changed the feature to install on Windows XP.

<Component Id="WallpaperPermW7" Guid="{c6427f8f-ce18-4675-9ea4-3292c18c897f}" Feature="W7Feature">
    <RegistryValue Id="WallpaperRegW7" Root="HKLM" Key="Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background" Name="OEMBackground" Value="1" Type="integer" KeyPath="yes">
</Component>

EDIT

Thanks Yan, I can see the registry going into the WoW folder now,

But, I want it to install it in the same path for both 64 and 32 bit systems if I add the Win64=”yes” attribute then it won’t install on 32 bit systems will it?

Is there a way around not having two packages?

  • 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-05-20T05:32:52+00:00Added an answer on May 20, 2026 at 5:32 am

    I take it your package is 32-bit, and hence on 64-bit systems the path you specify in the “key” attribute of RegistryValue element is mapped to a different hive:

    Software\Wow6432Node\Microsoft…

    instead of

    Software\Microsoft…

    That’s why you don’t see your value in place you expect it to be.

    In order to correct this you’ll have to mark your component as 64-bit (Win64=’yes’), but this will mean that the entire package is 64-bit, and as a result you’ll have to author a pair of packages, one for 32-bit, one for 64-bit… Probably, you can revise your requirements to avoid this.

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

Sidebar

Related Questions

The following code works as expected on CentOS and Ubuntu O/s but not on
The following code works with Visual Studio 2008 but not with GCC/G++ 4.3.4 20090804.
The following code works as expected in IE8 and Safari4, but not in Firefox3.6
The following code works great in IE, but not in FF or Safari. I
I have the following code in a CDialog. This code works perfectly on Windows
The following code works only on mac, but not on windows7. perl -e print
The following code works, but I can't figure out what's going on memory-wise. Where
The following code works, but I'm curious as to why I need the Path
Running the following code on Windows 7 x64 #include <stdio.h> #include <errno.h> int main()
The following code works fine in Windows: subprocess.Popen([PATH_TO_G++]/g++ file.cpp -o file.exe) However in Linux

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.