# “MikTeX Compiler Driver did not succeed” Fatal texify

I started working with LaTeX a few weeks ago and out of a sudden, MikTeX does not work any more, even though I did not change anything from one compilation to the next.

I tried everything - all recommendations in other forums and I still could not solve it. Please find below the output I get.

Any help would be greatly appreciated. Kind regards, Fran

It shows this error message

``````Sorry, but "MiKTeX Compiler Driver" did not succeed.
The log file hopefully contains the information to get MiKTeX going again:
C:\Users\AppData\Local\MiKTeX\2.9\miktex\log\texify.log
``````

When I go to the log file, it shows this :

``````2018-10-30 16:30:13,020Z INFO  texify - starting with command line: "C:\Users\\AppData\Local\Programs\MiKTeX 2.9\miktex\bin\x64\texify.exe" --pdf --synctex=1 --clean Thesis_001.tex
2018-10-30 16:30:34,781Z FATAL texify - TeX engine failed for some reason (see log file).
2018-10-30 16:30:34,781Z FATAL texify - Info:
2018-10-30 16:30:34,781Z FATAL texify - Source: Programs\MiKTeX\texify\mcd.cpp
2018-10-30 16:30:34,781Z FATAL texify - Line: 1479
2018-10-30 16:30:40,460Z INFO  texify - starting with command line: "C:\Users\AppData\Local\Programs\MiKTeX 2.9\miktex\bin\x64\texify.exe" --pdf --synctex=1 --clean Thesis_001.tex
2018-10-30 16:30:43,808Z FATAL texify - TeX engine failed for some reason (see log file).
2018-10-30 16:30:43,808Z FATAL texify - Info:
2018-10-30 16:30:43,808Z FATAL texify - Source: Programs\MiKTeX\texify\mcd.cpp
2018-10-30 16:30:43,808Z FATAL texify - Line: 1479
2018-10-30 16:31:36,997Z INFO  texify - starting with command line: "C:\Users\AppData\Local\Programs\MiKTeX 2.9\miktex\bin\x64\texify.exe" --pdf --synctex=1 --clean bibMPhilthesis.bib
2018-10-30 16:31:41,236Z INFO  texify - starting with command line: "C:\User\AppData\Local\Programs\MiKTeX 2.9\miktex\bin\x64\texify.exe" --pdf --synctex=1 --clean bibMPhilthesis.bib
2018-10-30 16:31:47,942Z FATAL texify - A required utility could not be found. Utility name: makeinfo.
2018-10-30 16:31:47,943Z FATAL texify - A required utility could not be found. Utility name: makeinfo.
2018-10-30 16:31:47,943Z FATAL texify - Info:
2018-10-30 16:31:47,943Z FATAL texify - Source:
2018-10-30 16:31:47,943Z FATAL texify - Line: 0
2018-10-30 16:31:54,933Z INFO  texify - starting with command line: "C:\Users\AppData\Local\Programs\MiKTeX 2.9\miktex\bin\x64\texify.exe" --pdf --synctex=1 --clean Thesis_001.tex
2018-10-30 16:31:55,456Z FATAL texify - TeX engine failed for some reason (see log file).
2018-10-30 16:31:55,456Z FATAL texify - Info:
2018-10-30 16:31:55,456Z FATAL texify - Source: Programs\MiKTeX\texify\mcd.cpp
2018-10-30 16:31:55,456Z FATAL texify - Line: 1479
``````
• Try to compile your document not with `texify`, but only with pdfLaTeX. If there are errors the output you get from a direct LaTeX run are often much more useful than those reported by `texify`. Ideally you would run the commands in the command line, but your editor should usually have an option to select only `pdfLaTeX` instead of a combined call (e.g. "pdfLaTeX + BibTeX + pdfLaTeX (x2)" or similar) that calls `texify`. – moewe Oct 30 at 16:51
• (1) welcome, (2) as you'll see in basically all other questions here, we cannot do much without code from your side. (3) did you have a look in the log file to your document not texify – daleif Oct 30 at 16:53
• Thanks! I tried running this with pdfLaTeX and the first fatal error that comes is 2018-10-30 16:53:12,673Z FATAL miktex-pdftex - Administrative mode cannot be enabled (makes no sense) because this is not a shared MiKTeX setup. That appears several times. Is there an easy fix to this? Thanks – Franziska Oct 30 at 16:57
• I tried it all in overleaf and it works perfectly there, so my code seems to work. Is this a programme issue? Thanks – Franziska Oct 30 at 16:59
• `FATAL miktex-pdftex - Administrative mode cannot be enabled (makes no sense) because this is not a shared MiKTeX setup` suggests that MikTeX somehow thinks you are running the executables like pdfLaTeX in admin mode (which you really should not and you should not have to do that either). It does indeed look as if your installation or some other configuration is damaged. Unfortunately it is trick to figure out what exactly is wrong from afar. – moewe Oct 30 at 19:00