# XeLaTeX Errors on Windows 7 [closed]

I'm trying to get a minimal XeLaTeX document to compile in Windows 7 with MiKTeX 2.9. I have updated all of my installed MikTeX packages and am still getting many errors during compilation.

\documentclass[10pt]{article}

\usepackage{fontspec,lipsum}

\listfiles

\begin{document}

\section{Introduction}

\lipsum[1]

\end{document}


I get a working document after hitting return through a lot of errors, but it has some debugging comments at the beginning of the pdf. See below:

Here are the first errors of the log file:

\l_fontspec_tmp_int=\count122
LaTeX Info: Redefining \itshape on input line 1893.
LaTeX Info: Redefining \slshape on input line 1897.
LaTeX Info: Redefining \scshape on input line 1901.
LaTeX Info: Redefining \upshape on input line 1905.

("C:\Program Files\MiKTeX 2.9\tex\latex\fontspec\fontspec.cfg"
! Undefined control sequence.
<argument> \c_keys_code_root_tl
fontspec/Ligatures/Historical
l.8 ...tureoption{Ligatures}{Historic}{Historical}

?
! Undefined control sequence.
<argument> \c_keys_code_root_tl
fontspec/Ligatures/Historic
l.8 ...tureoption{Ligatures}{Historic}{Historical}

?
))) (C:\Users\desktop\AppData\Roaming\MiKTeX\2.9\tex\latex\lipsum\lipsum.sty
Package: lipsum 2011/04/14 v1.2 150 paragraphs of Lorem Ipsum dummy text
\c@lips@count=\count123
)
Requested font "Adobe Garamond Pro" at 10.0pt
-> C:/Windows/Fonts/AGaramondPro-Regular.otf
Requested font "Adobe Garamond Pro/ICU" at 10.0pt
-> C:/Windows/Fonts/AGaramondPro-Regular.otf

! Undefined control sequence.
\fontspec_get_features:n ...st ,#1}\str_if_eq:xxF
{\l_fontspec_hexcol_tl \l_...

?

! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
...


The complete logfile can be found here: template.log

I get the same results using any number of installed system fonts. I'd like to get the document to compile correctly without errors and to leave out the extra information at the beginning of the resultant pdf.

-

## closed as too localized by lockstep, Jubobs, Speravir, Kurt, Martin SchröderApr 7 '13 at 20:57

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Welcome to TeX.sx! –  texenthusiast Apr 7 '13 at 18:48
Update your system. –  Ulrike Fischer Apr 7 '13 at 19:02
Your fontspec (you: 2012/05/06 v2.2b – me: 2013/03/16 v2.3a) and xetex.def (you: 2009/11/22 v0.94 – me: 2013/02/04 v0.95) are older than mine, while your xparse (you: 2013/03/12 v4467 – me: 2012/11/21 v4332) is more recent. Strange. One way or the other, a xetex.def from 2009 doesn’t sound good. –  doncherry Apr 7 '13 at 19:10
Never mind the xparse, that was just a quirk of my system. Now I’m at v4467 as well and the picture is clear: Your system is indeed not up to date and you should update. See How do I update my TeX distribution?. –  doncherry Apr 7 '13 at 19:17