准备系统时无法通过第二次启动或以其他方式使用Xbootmgr.exe获取跟踪 [英] Unable to get past second boot when preparing system or otherwise obtaining traces with Xbootmgr.exe

问题描述

我目前正在使用Windows 7旗舰版（x64）上的Windows 7 SDK运行Windows性能分析器v 4.6。

我目前正在尝试优化此系统的启动过程。不幸的是，命令"xbootmgr.exe -trace boot -prepSystem"在第二次重启时产生以下错误：

"等待300秒后等待Win7RTM物理预取器。
无法等待预取器。
找不到kenrel记录器在活动记录器列表中。
无法在活动记录器列表中找到用户模式记录器。"
它管理一次重启，但在第二次重启时始终失败并显示此错误。 />
有没有人有任何想法或可能的解决方案？很多人赞赏。

I'm currently running Windows Performance Analyzer v 4.6 from the Windows 7 SDK on Windows 7 Ultimate (x64).

I'm currently attempting to optimize this system's boot process. Unfortunately, the command "xbootmgr.exe –trace boot –prepSystem" generates the following error on the second restart:

"Gave up waiting for Win7RTM physical prefetcher after 300 seconds.
Could not wait for prefetcher.
Couldn't find kenrel logger in active logger list.
Couldn't find user-mode logger in active logger list."

It manages one restart, but consistently fails with this error on the second restart.

Does anyone have any ideas or a possible solution?
Much appreciated.

推荐答案

我使用运行Win 7 x64家庭高级版（库存注册设置）的新HP TouchSmart 300机箱遇到了同样的问题。
我尝试了以下命令："xbootmgr -trace rebootcycle -noprepreboot -verbosereadyboot"
自动重启后，我收到了与你相同的信息（也在xbootmgr.log中重现）

加上常量BSOD 使用DRIVERS标志和命令  xbootmgr -trace boot，我觉得xbootmgr（来自4.6版本的Windows性能套件）并不完全符合Win 7 x64的库存版本（至少家庭高级版）。

EDIT_1：

好的，我找到了解决这些错误消息的解决方案，并且" xbootmgr -trace rebootcycle -noprepreboot"工作：
我进入注册表，打开密钥：HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet \services \ SysMain
并将Start数据从原来的3（手动启动）更改为0（启动开始）。请注意，将其设置为2（自动启动）将不起作用。
（我建议在修改注册表之前创建一个恢复点）。

EDIT_2：

由MS建议的引导碎片整理优化这里，带有" xbootmgr -trace rebootcycle -prepsystem"在第6次重启结束时xbootmgr.log中的以下消息仍然存在问题：
[2010/02 / 20-11：34：33.473]启动尝试＃1对磁盘进行碎片整理...
[2010/02 / 20-11：34：39.525] ProcessIdleTasks返回。
[2010/02 / 20-11：34：39.525]碎片整理失败 - 状态键为'否'，错误描述为'缺少注册表参赛作品。重试。
[2010/02 / 20-11：34：39.525]启动尝试＃2对磁盘进行碎片整理... [2010/02 / 20-11：34：45.126] ProcessIdleTasks返回。< br> [2010/02 / 20-11：34：45.126]无法进行碎片整理 - 状态键为"否"，错误描述为"缺少注册表项"。重试。
[2010/02 / 20-11：34：45.126]启动尝试＃3对磁盘进行碎片整理...
[2010/02 / 20-11：34：50.664] ProcessIdleTasks返回。< br> [2010/02 / 20-11：34：50.664]碎片整理失败 - 状态键为"否"，错误描述为"缺少注册表项"。正在重试。
[2010/02 / 20-11：34：50.664]启动尝试＃4对磁盘进行碎片整理...
[2010/02 / 20-11：34：56.951] ProcessIdleTasks返回。< br> [2010/02 / 20-11：34：56.951]无法进行碎片整理 - 状态键为"否"，错误描述为"缺少注册表项"。重试。
[2010/02 / 20-11：34：56.951]启动尝试＃5对磁盘进行碎片整理...
[2010/02 / 20-11：35：03.081] ProcessIdleTasks返回。< br> [2010/02 / 20-11：35：03.081]碎片整理失败 - 状态键为"否"，错误描述为"缺少注册表项"。重试。
[2010/02 / 20-11：35：03.081] 5次尝试后无法对磁盘进行碎片整理。
[2010/02 / 20-11：35：03.081] PrepareSystem失败。
[2010/02 / 20-11：35：03.081]停止跟踪... [2010/02 / 20-11：35：03.737]无法在活动记录器列表中找到内核记录器。
[2010/02 / 20-11：35：03.737]无法在活动记录器列表中找到用户模式记录器。
[2010/02 / 20-11：35：03.737]取消注册自动运行.. 。[2010/02 / 20-11：35：03.737]完成自动运行更改。
 
EDIT_3

好的，我可能找到了解决方案是完成完整的6个重新启动循环并启动碎片整理优化：

在HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft &\\Dfrg \ BootOptimizeFunction下我原来只有2个字符串值：

• " OptimizeComplete"字符串数据为"否"的字符串数据


• " OptimizeError"字符串数据为"Missing Registry Entries"

Hi,

I got the same problem with a new HP TouchSmart 300 box running Win 7 x64 Home Premium Edition (stock registry settings).
I tried the following command:"xbootmgr -trace rebootcycle -noprepreboot -verbosereadyboot"
After automatic reboot I got the same message as you did (also reproduced in xbootmgr.log)

Add to this the constant BSOD when using the DRIVERS flag with the command  xbootmgr -trace boot, I got the feeling that xbootmgr (from the 4.6 edition of the Windows Performance Kit) is not fully compliant with a stock version of Win 7 x64 (Home Premium edition at least).

EDIT_1:

OK, I found a solution to get rid of these errors messages and have" xbootmgr -trace rebootcycle -noprepreboot" working:
I went into the registry, opened the key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SysMain
and changed the Start data from the original 3 (manual start) to 0 (boot start). Notice that setting it to 2 (automatic start) wouldn't work.
(I advise to create a restoration point before modifying the registry).

EDIT_2:

The boot defrag optimization, suggested by MS here , with" xbootmgr -trace rebootcycle -prepsystem" still has problems with the following messages in xbootmgr.log at the end of the 6th reboot:
[2010/02/20-11:34:33.473] Launching attempt #1 to defragment disk...
[2010/02/20-11:34:39.525] ProcessIdleTasks returned.
[2010/02/20-11:34:39.525] Failed to defrag - status key is 'No', error description is 'Missing Registry Entries'. Retrying.
[2010/02/20-11:34:39.525] Launching attempt #2 to defragment disk...
[2010/02/20-11:34:45.126] ProcessIdleTasks returned.
[2010/02/20-11:34:45.126] Failed to defrag - status key is 'No', error description is 'Missing Registry Entries'. Retrying.
[2010/02/20-11:34:45.126] Launching attempt #3 to defragment disk...
[2010/02/20-11:34:50.664] ProcessIdleTasks returned.
[2010/02/20-11:34:50.664] Failed to defrag - status key is 'No', error description is 'Missing Registry Entries'. Retrying.
[2010/02/20-11:34:50.664] Launching attempt #4 to defragment disk...
[2010/02/20-11:34:56.951] ProcessIdleTasks returned.
[2010/02/20-11:34:56.951] Failed to defrag - status key is 'No', error description is 'Missing Registry Entries'. Retrying.
[2010/02/20-11:34:56.951] Launching attempt #5 to defragment disk...
[2010/02/20-11:35:03.081] ProcessIdleTasks returned.
[2010/02/20-11:35:03.081] Failed to defrag - status key is 'No', error description is 'Missing Registry Entries'. Retrying.
[2010/02/20-11:35:03.081] Failed to defragment disk after 5 attempts.
[2010/02/20-11:35:03.081] PrepareSystem failed.
[2010/02/20-11:35:03.081] Stopping trace...
[2010/02/20-11:35:03.737] Couldn't find kernel logger in active logger list.
[2010/02/20-11:35:03.737] Couldn't find user-mode logger in active logger list.
[2010/02/20-11:35:03.737] Unregistering auto-run...
[2010/02/20-11:35:03.737] Completed auto-run change.
 
EDIT_3

OK, I may have found a solution to have the full 6 rebootcycles completed and boot defrag optimised:

Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction
I had originally just 2 string values:

• "OptimizeComplete" with a string data of "No"
• "OptimizeError" with a string data of "Missing Registry Entries"

• " Enable"用一个字符串 数据"Y"


• " LcnStartLocation"字符串数据为0


• " LcnEndLocation"字符串数据为0

• " BootFilesOptimized"使用双字数据1

这篇关于准备系统时无法通过第二次启动或以其他方式使用Xbootmgr.exe获取跟踪的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！