STAR WARS Episode I Racer cannot start if installed in non-C: drive

Product: EA Desktop
Platform:PC
Error Report ID (learn how to create an Error Report ID in the sticky post) e1223f26-8749-4387-991f-a0905a3e829a
Which client functionality are you experiencing this bug with? Launch Game
When did this happen? (dd.mm.yy hh:mm) 10.12.20 00:50
Summarize your bug If the game install location is not on C: drive, for example installed to "D:\EA Games\STAR WARS Episode I Racer", then launching the game from EA Desktop fails with error message with the game asking to insert the CD-ROM. This is due to a bug in the generated launcher batch script which is not including drive change before the working directory change.
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? Install STAR WARS Episode I Racer to D: drive, try to launch the game.
What happens when the bug occurs? Error that CD-ROM is not inserted.
What do you expect to see? I would expect the game to launch.

‌

Apparently EA Desktop creates a temporary batch file to set up the game environment for the administrator user, but this batch file generation is missing the drive change. Essentially, the contents in the file are something like this:

cd "D:\EA Games\STAR WARS Episode I Racer\common"
"D:\EA Games\STAR WARS Episode I Racer\common\SWEP1RCR.EXE"

While the correct form should be

D:
cd "D:\EA Games\STAR WARS Episode I Racer\common"
"D:\EA Games\STAR WARS Episode I Racer\common\SWEP1RCR.EXE"

To change the current working drive letter so that the "cd" command has the appropriate effect.