Installing Microsoft SQL Server Management Studio Express in Windows Vista or Seven: Error 29506

This is a problem about privileges. Probably the installer performs the latests tasks without using elevation.

Solution is very simple: run the installer from an elevated command prompt.

  1. Click Start.
  2. Type cmd end press CTRL+SHIFT+ENTER and accept the elevation.
  3. Execute the installer from there (just type path and filename).

This works on Windows Vista and, of course, on Windows 7.

If using a 64 bit version, please note you will have to use the 64 bit version of cmd.exe, which is located in c:\Windows\SysWoW64 instead on c:\Windows\System32, so just write c:\Windows\SysWoW64\cmd instead of just cmd (thanks to Pierre Boucher for this)


  1. tqz wrote:

    working! Very good and thanks a lot for tooltip !

  2. Magneton wrote:

    Working very vell! Thx.

  3. Gerard wrote:

    I did this and it worked, thanks so much i just installed vista a few hours ago and you saved my life, i was about going back to xp, but could you tell me this doesnt cause any problem creating dbs and developing an aplication from visual studio and windows vista?

  4. Sid wrote:

    Yes, it does not create any problem creating dbs and developing applications.
    The only thing that is different from Windows XP is that if you want to put the mdf file inside a user directory (i.e. c:\users\username\documents) you will need to manually set the ACLs.

  5. Sheetal wrote:

    Thanks for this tip. This was helpful

  6. Pierre Boucher wrote:

    Thanks! I must add that if you have a 64bit Vista like mine, you need to use the 64bit version of the cmd program. To do that, just write the full path to the application (ex: c:\windows\syswow64\cmd). The rest of the procedure is the same.

  7. Jacob Sandin wrote:

    Hi I had no problem installing the x64 SQL with elivated 32bit cmd.exe.

    But I had no idea that both 32bit and 64bit existed. Thanx for that info Pierre.

  8. Tino wrote:


    This helped me out :)

  9. Mike wrote:

    isn’t the 64bit cmd.exe confusingly in system32? I remember reading that recently

  10. 5roofNono wrote:

    yeaaaaaaaa, i worked good

  11. fasii wrote:

    I have same message when I was trying to install Microsoft SQL Server Management Studio Express: Error 29506,

    I love guys for that tip, by using “cmd“ it’s working now great thanks

  12. Mannish wrote:

    Great tip, thanks!

  13. cosophy wrote:

    ok well done!

  14. Eng.Ahmad Othman wrote:

    It works, thank you very much….

  15. Imran wrote:

    It worked!!!

  16. Jeroen Bakker wrote:

    SUPER!!! Trick.

    One other problem, when i type cmd.exe in vista, it opens, then disappers. But I managed to open up another prompt anyway

  17. Ryan wrote:

    Great tip. Was a little confused about the ctl+shift+enter, but the realised that you open the command prompt with that key combo once its highlited. thanks again.

  18. Sid wrote:

    @Ryan: Nope. CTRL+SHIFT+ENTER launches the executable / file you typed with elevation.
    The command prompt opens because you typed “cmd” (that stands for command prompt).

  19. Daryl wrote:

    Worked for me. This type of permission issue should have been addressed by MS. :)

  20. Sam wrote:

    sort and sweet, excellent!

  21. Robert wrote:

    Worked like a charm! Thanks!

  22. Applehead wrote:

    Thank you! Same problem persists in windows 7, and this trick works perfectly :-)

  23. io wrote:

    i cant used it i dont know why
    i dont know what to do
    how do i write de path or de filename
    what do i have to write… help me
    im a disaster

  24. patibandha wrote:

    thanks man.. this work for me in case of window 7 64 bit

  25. chris M wrote:

    For Windows 7 you have to use the 64 CMD and then run this as administrator. So I did the following…
    1. Right click on desktop and click NEW – SHORTCUT
    2. Create shortcut to C:\Windows\SysWOW64\cmd.exe
    3. Right click on the new shortcut and Run AS ADMINISTRATOR
    4. Enter full path and file name:
    e.g. C:\Users\[YOUR NAME]\Downloads\SQLServer2005_SSMSEE_x64.msi
    Where [YOUR NAME] is the windows user you are using.

  26. IceMan wrote:

    Hello Chris..

    There are lot of solutions published on many sites but none explained in detail for Windows 7, (like mention specific to use 64bit of cmd.exe) I was using the normal cmd but was erroring out. This worked for me. Thanks a lot.

  27. Anonymous wrote:

    Thanks Chris M

    Yes this works awsome on 7 64 bit

  28. megy wrote:

    I have the same problem on win 7. Can anyone help me? I did not manage to solve this problem bye my self.

    My mail is and hope that someone will read this and try with TeamViewer get in my computer and fix it. I am hopeless :o (

  29. vishal wrote:

    Interestingly, the solution on this page didn’t work for me verbatim. Instead I had to browse to the folder containing the 64 bit version of cmd and then right click the executable and select Run as administrator. I accepted the elevation and then ran the msi for SQL Server Management Studio – This did the trick.

    Thanks to all for posting the solution!

    Whoops – Just noticed that Chris M also posted a similar solution.

  30. dedobe wrote:

    Very helpful. Thanks!

  31. Anonymous wrote:

    Thanx a lot.

  32. Anonymous wrote:

    This method is not working on my pc.

  33. mark wrote:

    Thank you so much! It worked after hours of stress.

  34. crty wrote:

    M$ is one piece of shit…

  35. Goodluck wrote:

    this really helped me….Chris, thnx a lot for the information… :)

  36. Glenn wrote:

    Wow. What a dog. I download it 4 times, tried elevated privledges in many ways and still could not get it to work (grrr!) – then I saw vishal’s post and tried that and it worked!
    So in Win7 64 bit you NEED to find the ” C:\Windows\SysWOW64\cmd.exe” file and right-click and run as admin and THEN it’ll work. Interestingly if you do that you get a CMD box set to c:\Windows\Sys32 where as running it directly it comes up with c:\SysWOW64. Thanks guys!

  37. Chris wrote:

    Thanks you for installing MSQL server quide.

  38. Sweta wrote:

    thnk you….really worked!!! :)

  39. B. A. Shelton wrote:

    Thanks for the tip!

    Two nitpicks with everyone claiming that the SysWoW64 version is necessary: 1) SysWoW64 is the “Windows 32-bit on Windows 64-bit” subsystem and this location contains Windows 32-bit on 64-bit helpers (see the Wikipedia article for references). 2) There is no functional difference between the cmd.exe contained in System32 versus the one in syswow64. They are identical (md5sum from a Cygwin shell), and here’s proof:

    bshelton@/cygdrive/c/windows/syswow64$ md5sum cmd.exe
    ad7b9c14083b52bc532fba5948342b98 *cmd.exe

    bshelton@/cygdrive/c/windows/syswow64$ md5sum ../system32/cmd.exe
    ad7b9c14083b52bc532fba5948342b98 *../system32/cmd.exe

    Furthermore, Cygwin reports cmd.exe as a 32-bit binary:

    bshelton@/cygdrive/c/windows/system32$ file cmd.exe
    cmd.exe: PE32 executable (console) Intel 80386, for MS Windows

    Compared to others which appear to be 64-bit:

    bshelton@/cygdrive/c/windows$ file write.exe
    write.exe: PE32+ executable (GUI) x86-64, for MS Windows

    So to put this to rest: Regardless of which cmd.exe you’re running, you are running identical files, both of which appear to be built for the x86 architecture. If you’re having difficulty with one, it’s exceedingly likely that you haven’t properly elevated the command prompt’s permissions and has nothing to do with the target arch (in fact it can’t!).

  40. B. A. Shelton wrote:

    As an addendum to my previous post: I was wrong about the bit-ness. It appears that Cygwin does not, in fact, report the correct information. I had an inkling of an idea that I may have been wrong (I was) and copying both files over to my file server, then compared them:

    [sagittarius:~]$ md5sum *cmd.exe
    5746bd7e255dd6a8afa06f7c42c1ba41 system32-cmd.exe
    ad7b9c14083b52bc532fba5948342b98 syswow64-cmd.exe

    However, I was still right about one thing: If you examine the output of Windows’ task manager, cmd.exe from System32 appears as a native app; running cmd.exe from SysWoW64 will flag it with the “*32″ suffix indicating that it’s running under 32-bit emulation.

    My conclusion is different: It is feasible (although Windows isn’t really my native OS) that the reason some people had success with the SysWoW64 version because of some weirdness in the emulation layer that running a 32-bit version of cmd.exe would fix.

    Please disregard my previous post, at least partially. Cygwin clearly didn’t report the correct information to me, and I didn’t bother to double check it.

    Either way, Sid’s original post was spot on. So bear in mind: If you’re running cmd.exe from SysWoW64, you are running the *32-bit* version, NOT 64-bit as some other posters have indicated. The MD5 sum of the 32-bit version should be ad7b9c14083b52bc532fba5948342b98, which you can verify yourself.

  41. Niharika wrote:

    sorry but this is not work in my system ,,, so plz any one can help me

  42. Jose Diaz wrote:

    Yes. This worked really well! Thanks for the tip. Right-clicking on the cmd executable and selecting Run as Administrator also works.

  43. WLBII wrote:

    can also be installed from the elevated taskmgr, just designate the path to the msi file.

  44. Manasi wrote:

    Hey Thanks a ton!
    it worked!

  45. Noufiya wrote: works!!!!!!!!!!!!!!!