0

I'm running MikTeX 2.9 (64-bit) on a new Windows 10 laptop. For some reason, when I run LaTeX (or PDFLaTeX), it terminates operation upon encountering any LaTeX errors (such as unknown commands), rather than giving an interactive prompt for each error. For instance, it fails with the following basic example:

\documentclass{article}
\begin{document}
Hello hello hello
\asdfsfd
Blah blah blah
\end{document}

The output looks like this:

! Undefined control sequence.
l.9 \asdfsfd

?
Sorry, but pdflatex did not succeed.

The log file hopefully contains the information to get MiKTeX going again:

  C:\Users\Adam Levine\AppData\Local\MiKTeX\2.9\miktex\log\pdflatex.log

And what shows up in the log file is:

2020-07-27 13:16:52,269-0400 INFO  pdflatex - this process (14176) started by 'cmd' with command line: pdflatex test.tex
2020-07-27 13:16:52,278-0400 INFO  pdflatex - allowing known shell commands
2020-07-27 13:16:52,278-0400 INFO  pdflatex - enabling input (output) from (to) processes
2020-07-27 13:16:52,312-0400 INFO  pdflatex - going to create file: pdflatex.fmt
2020-07-27 13:16:52,348-0400 INFO  pdflatex.core - start process: initexmf --enable-installer --dump-by-name=pdflatex --engine=pdftex
2020-07-27 13:16:55,252-0400 FATAL pdflatex.core - MiKTeX encountered an internal error.
2020-07-27 13:16:55,252-0400 FATAL pdflatex.core - Data: 
2020-07-27 13:16:55,252-0400 FATAL pdflatex.core - Source: Libraries\MiKTeX\TeXAndFriends\inputline.cpp:627
2020-07-27 13:16:55,252-0400 FATAL pdflatex - MiKTeX encountered an internal error.
2020-07-27 13:16:55,252-0400 FATAL pdflatex - Info: 
2020-07-27 13:16:55,252-0400 FATAL pdflatex - Source: Libraries\MiKTeX\TeXAndFriends\inputline.cpp
2020-07-27 13:16:55,252-0400 FATAL pdflatex - Line: 627
2020-07-27 13:16:55,253-0400 INFO  pdflatex - this process (14176) finishes with exit code 1
2020-07-27 13:16:55,254-0400 WARN  miktex.core - still open: test.tex
2020-07-27 13:16:55,254-0400 WARN  miktex.core - still open: test.aux
2020-07-27 13:16:55,254-0400 WARN  miktex.core - still open: test.log

I've never encountered this problem on any previous computer. I can work around the issue by using --nonstopmode as an option in the compiler, so that's there's no interaction, but I would ideally like to be able to have the interactive mode run properly so that I can debug as it goes. This isn't a problem when using the alternate compilers (XeLaTeX or LuaLaTeX).

I'd appreciate any suggestions.

  • 1
    Update, there was bug with this behaviour some weeks ago. But for me it currently works fine. – Ulrike Fischer Jul 27 at 17:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.