[Windows] Unable to create recovery image using Chromebook Recovery Utility - "Unable to unzip file..." |
||||||
Issue descriptionApp Version: 3.1.6 Chrome Version: 60.0.3112.32 Beta OS version: Windows 10: 10.0.10586 What steps will reproduce the problem? (1) Open the Recovery tool (2) Start the image creation process. What is the expected output? Should able to create the recovery stick. What do you see instead? Getting "Unable to unzip file. Please try again" message in step3. Note: submitted feedback report.
,
Jun 15 2017
Not able to reproduce on Mac with chrome version 60.0.3112.32
,
Jun 16 2017
,
Jun 16 2017
Five different boards builds downloads were initiated, and all failed at this stage 3 of 3 - Unzip file. Can somebody try on different Windows machine to create recovery stick for any board?
,
Jun 16 2017
,
Jun 16 2017
,
Jun 16 2017
I've kicked off a local Windows build and will try to repro. Not sure the OS-Chrome tag is an appropriate addition, as this sounds like a Windows bug.
,
Jun 16 2017
Being unable to unzip could be a disk space issue. Can you verify? The image is downloaded to the Downloads directory now though it is cleaned up after success/failure, but during the process you should be able to see it.
,
Jun 28 2017
Could any one from Platform>Apps>RecoveryTool team please have a look into this issue as it has been marked as a stable blocker. Thanks...!!
,
Jul 4 2017
Gentle Ping! Some one from Platform>Apps>RecoveryTool team please have a look into this issue as it has been marked as a stable blocker. Thank You!
,
Jul 6 2017
Took a look at the Windows machine and it looks like the C: is basically full. Suggest clearing up space, around 4GB to be safe, and trying again. If the problem persists please let me know. A lower priority bug should be created to improve the error message to check on space available on the hardrive/partition.
,
Jul 6 2017
It looks like files are not cleaned from user's AppData/Local/Temp directory after recovery stick is prepared, thus device was clogged. Freeing space helped and recovery tool proceeded successfully through all stages of Step 3.
,
Jul 6 2017
,
Jul 6 2017
As stephen suggested, we need a bug on better error messages. We can re-purpose this bug or create a new one.
,
Jul 6 2017
New bug referencing this one is preferred. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by sontis@chromium.org
, Jun 15 201791.7 KB
91.7 KB View Download