1502 RPi2更新失败 [英] 15026 update failure on RPi2

查看:69
本文介绍了1502 RPi2更新失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述


RPi2与RPi官方7"触摸屏。

RPi2 with RPi official 7" touch screen.

先前版本为15007.从设备门户,检查更新。等到下载和安装显示完成。使用的设备门户重置。然后装置显示正常的齿轮。 45分钟后,Windows启动但没有IoTCoreDetfaultApp。
显示为纯灰色,看起来根本没有输入。设备门户仅显示ConnectApp,IoTUAPOOBE,IoTOnboardingTask,ZWave Adapter无头主机。只有IoTOnboardingTask正在运行。 OOBE没有运行。等了5分钟。
屏幕上仍然没有,所以我使用Device Portal启动IOTUAPOOBE。它出现在屏幕上,但是众所周知,OOBE启动布局在7"官方展示。但这不是我所关心的。几分钟后,其他几个
应用程序出现在设备管理器中,但不是IoTCoreDefaultApp。也许另外5分钟过去,而OOBE只是坐在蓝屏上。此时我决定将OOBE设为默认应用并重新启动。重新启动后,按预期进入OOBE蓝屏。
还在等待几分钟,IoTDefaultCoreApp出现在应用程序管理器中,但没有显示在屏幕上(正如预期的那样,因为OOBE被设置为默认值)。但是OOBE仍然没有改变默认的蓝屏。在Apps管理器中,我告诉IoTCoreDefaultApp
开始。现在OOBE终于显示了语言的选择等等,我经历了这一点。然后我回到应用程序管理器,发现IoTCoreDefaultApp没有被OOBE设置为默认值,所以我手动更改了它。

Prior version was 15007. From device portal, checked for updates. Waited until download and install showed complete. Used device portal to reset. Device then showed gears like normal. 45 minutes later showed Windows startup but no IoTCoreDetfaultApp. The display was a solid gray color which looks like it has no input at all. Device portal showed only ConnectApp, IoTUAPOOBE, IoTOnboardingTask, ZWave Adapter Headless Host. Only IoTOnboardingTask was running. The OOBE was not running. Waited perhaps 5 minutes. Still nothing on the screen, so I used Device Portal to start IOTUAPOOBE. It appeared on the screen, but as you all know, the OOBE startup layout is poor on 7" official display. But that's not what I'm concerned about. A few minutes later, several other apps appers in device manager, but not IoTCoreDefaultApp. Perhaps another 5 minutes go by while OOBE just sits at its blue screen. At this point I decide to make OOBE the default app and reboot again. After reboot it comes up to OOBE blue screen as expected. Still waiting another few minutes and IoTDefaultCoreApp appears in the apps manager, but doesn't show on the screen (as expected because OOBE was set as default). But OOBE still doesn't change from the default blue screen. In Apps manager I tell IoTCoreDefaultApp to start. Now OOBE finally displays the choice of language, etc and I go through that. Then I go back to apps manager and see that IoTCoreDefaultApp was not set as default by OOBE, so I manually change that.

这是我怀疑发生的事情,如果这是正确的,请告诉我。在更新过程的齿轮部分之后,必须在OOBE出现之前完成其他任务。这留下7"树莓派官方触摸屏显示空白相当于
很长一段时间。 (这是一个非常糟糕的用户体验)。我等待5分钟或许没有等待足够长的时间来完成这些任务,并且最终(似乎还有15-20分钟的重新启动)IoTCoreDefaultApp会自己出现。

Here's what I suspect happened, please let me know if this is correct. After the gears portion of the update process, additional tasks have to be done before OOBE can appear. This leaves the 7" raspberry pi official touch screen display blank for quite a long time. (Which is a very poor user experience). My waiting 5 minutes perhaps wasn't waiting long enough for these tasks to complete and eventually (seems like about another 15-20 minutes of rebooting) IoTCoreDefaultApp would have appeared on it's own.

如果我的评估是正确的,然后在最初的Windows启动徽标和旋转圈后,Windows  10 IoT正在关闭VID接口到7"触摸屏显示,同时执行一些长任务。这是一种非常糟糕的用户体验。
一旦出现Windows徽标,屏幕就不应该像那样灰了。它应该至少显示一条关于仍在处理某些更新的消息。

If my assessment is correct then after the initial Windows startup logo and spinning circle, Windows 10 IoT is turning off the VID interface to the 7" touch screen display while it performs some long task. This is a very poor user experience. Once the Windows logo appears the screen should never gray out like that. It should at least show a message about still working on some updates.

推荐答案

嗨mjmeans,

Hi mjmeans,

我们有关于如何提交更新问题的非常具体的指导。请按照

https://social.msdn.microsoft.com/Forums/en-US/fad1c6a0-e578-44a7-8e8d -95cc28c06ccd / need-logs-if-your-device-hasnt-updated-to-latest-iotcore-version?forum = WindowsIoT
 报告您的体验,以便收集正确的数据以查看更新期间实际发生了

We have very specific guidance about how to file issues with update. Please follow the guidance at https://social.msdn.microsoft.com/Forums/en-US/fad1c6a0-e578-44a7-8e8d-95cc28c06ccd/need-logs-if-your-device-hasnt-updated-to-the-latest-iotcore-version?forum=WindowsIoT to report your experience so that the correct data can be collected to see what actually occurred during update.

此致,

IoTGirl


这篇关于1502 RPi2更新失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆