Windows 10 1511 PBR问题（硬重置）

本文介绍了Windows 10 1511 PBR问题（硬重置）的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我对新的Windows 10 1511 Build 10586有疑问，关于在完全取消用户数据期间的PBR。

实际上在新的OPK W10 1511 build 10586 （在以前的版本10240上未检测到任何问题）当apps.ppkg存在于文件夹c：\ update |\\customizations中时，重置过程存在问题。问题是在恢复结束时启动一个完全取消数据的PBR，而不是加载oobe，它重新启动阶段"应用PC设置"循环永久。

只有在系统中c：\ update @\\customizations中没有apps.ppkg时，才能成功完成这种重置。检测到没有关于保存用户数据和应用程序的刷新过程的问题。

您是否介意检查以在Windows 10 1511上测试重置恢复？我提醒，只发生在Windows 10 1511（x86和x64）（版本10586）上，我断言winre和scanstate工具是最后一个opk和adk发布的最新版本。

如果有关使用Scanstate的PBR和恢复程序有所改变或尝试帮助解决此阻止问题，请告诉我。

最好的问候。

Valerio。

解决方案

嗨Valerio，

我不确定这是否是开发问题。这个论坛是讨论Windows开发问题。我建议你在 answers.microsoft/en-上发布一个新帖子。 us /？auth = 1 以获得有效回复。

感谢您的理解。

问候，

I have a question about the new Windows 10 1511 Build 10586, concerning the PBR during a complete cancellation of user data.

Actually in the new OPK of W10 1511 build 10586 (no issue detected on previous build 10240) there is a problem on reset procedure when the apps.ppkg is present in the folder c:\recovery\customizations; the problem is that starting a PBR with complete cancellation of data the system at the end of the recovery instead of loads oobe it restarts launching again the phase "Applying PC Settings" in loop for ever.

That kind of reset completes successfully only if in a system there is no apps.ppkg in c:\recovery\customizations. No issue detected about the Refreshing Procedure holding user data and apps.

Would you mind to check to test reset recovery on Windows 10 1511 ? I remind, happens only on Windows 10 1511 (x86 and x64) ( build 10586) and I assert winre and scanstate tool are the newest version released with the last opk and adk.

Let me know if something is changed about the PBR and Recovery Procedure using Scanstate or try to help to solve this blocking issue.

Best Regards.

Valerio.

解决方案

Hi Valerio,

I am not sure if this is a dev problem. This forum is to discuss windows development issue. I would suggest you post a new thread on answers.microsoft/en-us/?auth=1 for effective response.

Thank you for understanding.

Regards,