pandoc not added to path on windows

[ibell]

As it says in the title, on windows, when I run the installer, pandoc folder is not added to the path. For me, it is installed in C:\Users\Belli\AppData\Local\Pandoc . The only way I could figure out the installation path was to go to start menu and figure out the path to the local documentation HTML file

[sheremetyev]

What is your Windows version? What version of Pandoc did you install?

[ibell]

Windows 7 64-bit, installer for 1.21.1 from http://code.google.com/p/pandoc/downloads/list

[bempelise]

Have the same issue here. Windows 8.1 64-bit.

[jgm]

Did you try closing the console window and opening a new one?

[bempelise]

Sorry for the delayed response.
The problem was solved for me after installing and re-installing pandoc 3
times. I did not change anything in particular. It was just that the last
time it was in my path and I could use it.
Cheers

On Fri, Jun 6, 2014 at 5:44 PM, John MacFarlane [email protected]
wrote:

Did you try closing the console window and opening a new one?

—
Reply to this email directly or view it on GitHub
https://github.com/jgm/pandoc/issues/1054#issuecomment-45358316.

[choosin]

I got the same problem and i found out that it actually set user variable PATH correctly.
However, Windows console seemed not reload the user variable even if I open/reopen cmd or powershell.

What I did to solve the problem:

1. Open "System properties" > "Advanced" > "Environment Variables..." window
2. Click "OK" without any modification

[jgm]

@sheremetyev, does @choosin's comment suggest any modification to the wix file?

[sheremetyev]

I think .wix file is fine. In my tests change to PATH is always visible in a new cmd instance.

@choosin, are you able to reproduce the problem? Could you list exact steps?

[jgm]

Apparently other WiX users have had similar problems, but this thread does not give a solution:

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setting-environment-variable-PATH-td2418484.html

http://blogs.technet.com/b/alexshev/archive/2008/03/28/from-msi-to-wix-part-13-installable-items-environment-variable.aspx

[AnthonyMastrean]

I'm on Windows 7 Pro SP1 x64 and I ran the installer in an elevated prompt with ALLUSERS=1 so that it installed into Program Files. The path is set incorrectly to the local user folder.

C:\Users\<username>\AppData\Local\Pandoc\

---

On further inspection, the correct machine PATH was set up, but an earlier user PATH was not removed! Maybe I had a bad uninstall? I guess the user path has precedence on the shell? Here's some of my evidence using .NET from a PowerShell session:

PS> [System.Environment]::GetEnvironmentVariable("PATH", "Process") -split ";" | ?{ $_.Contains("Pandoc") }
C:\Users\<username>\AppData\Local\Pandoc\

PS> [System.Environment]::GetEnvironmentVariable("PATH", "User") -split ";" | ?{ $_.Contains("Pandoc") }

PS> [System.Environment]::GetEnvironmentVariable("PATH", "Machine") -split ";" | ?{ $_.Contains("Pandoc") }
C:\Program Files (x86)\Pandoc\

This is actually kind of strange... I don't know how I got a persistent process PATH or how to remove it. I restarted my shell, but I haven't logged off/on or restarted my machine yet.

---

My bad, it took logging off/on again for all of my installer updates and PATH changes to get straightened out... my process PATH is now consistent with my machine PATH and all is good. If anything, my crazy experience is not consistent with the author of this issue... these MSI scripts are hard, but everything works with enough reboots :)

[jgm]

+++ Anthony Mastrean [Jul 14 14 14:44 ]:

I'm on Windows 7 Pro SP1 x64 and I ran the installer in an elevated
prompt with ALLUSERS=1 so that it installed into Program Files. The
path is set incorrectly to the local user folder.

C:\Users\eacwpku\AppData\Local\Pandoc\

@sheremetyev, is there a way to fix this?

[AnthonyMastrean]

@jgm @sheremetyev I was experimenting with all manner of local and machine installs today. I might have gotten myself into a pickle (see my edits above, I have to figure out why this process path persists). I actually got a good local PATH every time I installed with the default settings.

So, my report is actually unrelated to this issue, strictly speaking. It may even be evidence to the contrary. If you want, I'll open a separate issue for my comment and I can try to untangle my situation :D

[sheremetyev]

@AnthonyMastrean do you have local user folder in PATH in a new command prompt?

[AnthonyMastrean]

@sheremetyev after properly logging off/on I have only the correct machine PATH. There is no user PATH. Something got "stuck" in my process path between installs/uninstalls until I logged off/on.

PS> [System.Environment]::GetEnvironmentVariable("PATH", "Process") -split ";" | ?{ $_.Contains("Pandoc") }
C:\Program Files (x86)\Pandoc\

PS> [System.Environment]::GetEnvironmentVariable("PATH", "User") -split ";" | ?{ $_.Contains("Pandoc") }

PS> [System.Environment]::GetEnvironmentVariable("PATH", "Machine") -split ";" | ?{ $_.Contains("Pandoc") }
C:\Program Files (x86)\Pandoc\

[jgm]

I'm closing this since #1403 seems to be the same issue.

[tjbarbour]

Just in case someone else has the same issue as me, my issue was actually a corrupted PATH. Some other program (not pandoc) had accidentally inserted an extra quote ( " ) in the Path, rendering the following entries (including pandoc) ignored.

[shumeA]

What i have to do I'm using window 10 and it say's 'pandoc' is not recognized as an internal or external command, operable program or batch file?

[Opdoop]

@shumeA I have the same issue. Just restart computer solved the problem.