Here’s the scenario between the old work PC and the new work PC.
Old PC is 64-bit Windows 7 Enterprise, while new PC is 64-bit Windows 10 Education (1809). Old PC has 32-bit Office Pro Plus 2013 (MSI) installed, while new PC has 64-bit Office Pro Plus 2019 (C2R) installed.
With old PC, for years I have been able to start Excel from the command line (cmd.exe, not the Run box) within a batch file so as to automatically execute a macro to create a desired “pretty” XLS file (and save it as a PDF) from a CSV file. Even if I didn’t want to do a batch file operation, I could use cmd.exe to go to the C:\Program Files (x86)\Microsoft Office\Office15 directory, type Excel, and it would start with a blank workbook.
With new PC, using cmd.exe to go to the C:\Program FIles\Microsoft Office\root\Office16 directory, I know the excel.exe file is there, but when I type Excel, I immediately get a new command prompt in the cmd.exe window, and, about 20 seconds later, I get a pop-up box that says, “The application was unable to start correctly (0xc0000142).”
Searching the Web on that error code has not been helpful, and the suggestions of reinstalling Office that I did find don’t make sense, given that I can start Excel in the normal “Windows” way, or from the Run box, and it seems to work fine. (Office 2019 was pushed to new PC just earlier this week.)
Is it impossible for me to start my Excel 2019 from cmd.exe, requiring me to use the normal “Windows” way or at least the Run box? If so, is that due to an issue with Excel 2019, an issue with 64-bit Excel, an issue with Windows 10, or what?
I’m probably the only person I know at my work site that would even think of starting Excel from cmd.exe, but being able to do what I described within a batch file saves time and I’d like to be able to continue to do it even with this new PC.
Any info or suggestions would be appreciated. Thanks.
