# [Tex/LaTex] TexMaker stopped compiling but doesn’t show errors or new version of pdf

texmaker

I am using TexMaker to write my master thesis, already since almost six months. All of the sudden, the compiling stopped working. I press compile, everything seems as if it is compiling, but then once I click on view pdf none of my changes show up. I also doenst give me any error. And if I purposly include an error on the code, it doesnt show when I compile. I tried an old version that I was sure was working, and the same happens so I think the problem isn't in the code, but in the software. Any ideas?

When I run Path in my cmd window, this is what I get:

PATH=C:\Program Files (x86)\Intel\Intel(R) Management Engine
Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine
Components\iCLS\;C:\Program Files (x86)\NVIDIA
Corporation\PhysX\Common;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\windows\System32\OpenSSH\;C:\Program
Files\Intel\WiFi\bin\;C:\Program Files\Common
Files\Intel\WirelessCommon\;C:\Program Files\Microsoft SQL
Server\Client SDK\ODBC\110\Tools\Binn\;C:\Program Files
(x86)\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft
SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL
Server\120\DTS\Binn\;C:\Program Files (x86)\Windows Kits\8.1\Windows
Performance Toolkit\;C:\Program Files (x86)\Intel\Intel(R) Management
Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management
Engine
Components\DAL;C:\Users\maria\AppData\Local\Microsoft\WindowsApps;C:\Users\maria\AppData\Local\Programs\MiKTeX
2.9\miktex\bin\x64;C:\Program Files\TortoiseGit\bin;

If you are having problems with a previously working system because something upset the Path variables then you need to work through the following steps First check we have a pathing issue

This folder is the one that needs to be in the system path so we need to add or correct any corrupted existing entry.

There are two path settings in windows and when they are combined one can impact the other for the MiKTeX entry there should be NOTHING after the folder \bin (for32bit users) OR \bin\x64 (for 64bit users) so in this 64bit case we remove any thing after the 4

MiKTeX may not be the only wrong entry and will not work if it is lower than a bad entry so look at the adjoining ones in case they were corrupted or entered incorrectly

If MiKTeX is the last entry consider promoting it by using the "Move Up" button on the right

In windows 10 the easiest way to get access is via Cortana search

Once you have updated the paths to a suitable clean state it is important to reboot first so you check they will stick on next start-up but more importantly so all affected applications see the settings anew.

MiKTeX will most likely have been impacted by the path changes so it is best to fire up MiKTeX-console (as single user and if in dual setting also as admin).
From the TASKS pulldown run Refresh filename database and Refresh font map files.

Whilst in MiKTeX-console you can check that settings directories looks reasonable especially the lack of an error for link target directory

To retest all is good with paths use explore to browse to your directory that has a tex file and in the top address bar overwrite the entry with cmd then hit the enter key and you will be in a terminal console window for that directory > pdfLaTeX -version should respond with a version message and pdfLaTeX YourTeXfileName should stream a lot of compilation messages and eventually produce at the end of a good run a YourTeXfileName.pdf

If there were problems then the YourTeXfileName.log can help determine why so would be needed. At this stage the TeX engine is producing a PDF so should be working. Now attention can shift to the editor.

If TeX applications are confused by the changed system settings they may need to be reset so they can reconfigure.