我在虚拟机环境中使用WDS+MDT部署系统时，客户端报错且找不到任务序列

What ADK version are you using with MDT ?

What ADK version are you using ?

嗨**，欣玲，**

你的问题解决了吗？如果有，请考虑接受这个答案，因为它也帮助了其他有相同问题的人。谢谢你:)

多米克诉

Xin Ling

I see you successfully updated the Server 2025 Task Sequence ID to an alphanumeric format. However, the 14-digit number you mentioned (20260521172636) is the reason why the crash is still happening.

The issue is that the MDT wizard parses your entire task sequence list before it displays anything on the screen. Even though you fixed this specific Server 2025 task sequence, the script is still tripping over that massive number elsewhere in your deployment share.

To stop the wizard from crashing, you need to find and neutralize that 14-digit number.

1. Inspect All Other Task Sequences

• Open your Deployment Workbench and carefully check every other folder and task sequence.

Look for an old deployment, a capture sequence, or a backup sequence that might have been assigned 20260521172636 as its ID.

Change its ID to include letters, or delete it if it is no longer needed.

2. Manually Scrub the XML File

Navigate to your deployment share's control folder (e.g., \\wds\DeploymentShare$\Control\).

Open the TaskSequences.xml file in Notepad or another text editor.

Use Ctrl + F to search for 20260521172636.

If you find it attached to an old or broken <ts> (task sequence) block, carefully delete that entire block of code, save the file, and close it.

3. Strip the Math from the VBScript (Optional but Recommended)

Open \Scripts\DeployWiz_SelectTS.vbs.

Locate the sorting logic inside the InitializeTSList function.

Remove CInt() or CLng() from the variable comparisons. Allowing VBScript to compare the IDs strictly as raw text strings prevents it from ever attempting to calculate their mathematical value.

Once you have scrubbed that timestamp from the XML or updated the scripts, close the wizard on your client machine, reboot it, and PXE boot again. The wizard will bypass the math constraints and finally load your menu.

Domic V.

嗨**，欣玲，**

你遇到的错误是Microsoft部署工具包使用的遗留VBScript引擎中的文档限制。“错误：6 = 溢出”代码的出现是因为VBScript原生处理数值变量为16位整数，而其数学限制严格为32,767。当向导的初始化脚本，特别是在DeployWiz_SelectTS.vbs文件中，尝试读取你的部署变量时，纯数值任务序列ID超过该限制会强制进行数学转换，进程立即崩溃。如果你的 Hyper-V 虚拟机配置超过 32,767 兆字节的内存，也会出现几乎相同的溢出，因为底层的 ZTIUtility.vbs 脚本无法解析过高的硬件内存值。

要解决这个问题，打开你的部署工作台，将任务序列ID改为包含字母，比如“SRV-2025”，这样引擎就能安全地以字符串形式读取变量，而不是计算它。如果你在部署共享的 Scripts 文件夹中自定义了向导脚本以自动排序项目，你必须在记事本中编辑它们，并将所有 CInt（） 函数实例替换为 CLng（），这样脚本就能原生处理更大的数字。此外，确保虚拟机在初始成像阶段暂时将内存分配降至16GB或更少，以完全绕过硬件计算溢出。

最后，你应该知道，Microsoft 已经正式弃用 Microsoft 部署工具包，并且它完全不支持 Windows 11 和 Windows Server 2025。由于现代操作系统中底层的VBScript依赖正在被积极移除，依赖MDT将继续暴露未修补的架构缺陷。为了长期稳定性，强烈建议将部署基础设施迁移到Microsoft配置管理器或现代云配置流程，如Windows Autopilot。

如果你有任何问题，欢迎留言。

多米克诉