Error when running Windows Performance Toolkit log.cmd

Hoikkari-2301 20 Reputation points
2024-04-05T19:20:58.3+00:00

Hi,

I downloaded here this latest version of ADK which is made for Windows 11 23H2.

https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install

The Windows ADK 10.1.25398.1 (September 2023) and the Windows PE add-on for this ADK support the following OS releases:

  • Windows 11, version 23H2 and all earlier supported versions of Windows 10 and 11
  • Windows Server 2022

After this when I run this log.cmd I got error

603 was unexpected at this time.

This seems to be something syntax error? Or is this something else? Is there option run this log.cmd line by line to see where this error comes?

What is needed to do fix this?

And I am running CMD as Administrator rights.

Windows development Windows Performance Toolkit
Windows for business Windows Client for IT Pros Devices and deployment Set up, install, or upgrade
0 comments No comments
{count} votes

Accepted answer
  1. Gary Nebbett 6,216 Reputation points
    2024-04-11T14:17:35.3166667+00:00

    Hello Hoikkari-2301,

    The "problem" is that the space character has been set as the "digit grouping symbol" in the regional settings. The number 32603 is displayed as "32 603". The log.cmd script can cope with a comma (",") as the grouping symbol but it does not handle the other common symbols (dot, apostrophe and space).

    Gary

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. Simon Ren-MSFT 40,341 Reputation points Microsoft External Staff
    2024-04-08T09:47:45.7666667+00:00

    Hi,

    Thank you for posting in Microsoft Q&A forum.

    Could you please share the screenshot to narrow down the issue? Does the command complete successfully before the Windows ADK upgrade?

    Does the device run with the Microsoft .NET Framework 4.5 or later? For more information, please refer to:

    Windows Performance Toolkit

    Thanks for your time. Have a nice day!

    Best regards,

    Simon


    If the response is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Gary Nebbett 6,216 Reputation points
    2024-04-10T10:14:09.4366667+00:00

    Hello Hoikkari-2301,

    You could try making a copy of log.cmd (e.g. copy to testlog.cmd) and then editing the copy to remove or disable the @echo off command on the first line. Then run the new cmd file.

    Gary


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.