![]() I know that I am running Windows Insider Preview builds, which can be unstable and break existing applications. I have no idea what could be causing this, but I see that just very few certain people are experiencing it, which makes me think there is a common system setting or something along those lines. This is as much useful context as I can get:īut that doesn't seem to give much insight into what is actually happening. There is not, however if I add some breakpoints I can get a bit more information on what's happening. Regarding DevTools, is there a stack trace when expanding the Error object? Side note: The bug where the button just says "Starting." seems to be caused by a race condition or other oversight that is making the main application wait for the child process indefinitely. I can't get to the stage that would let me repro the original bug on a different storage device, either. I have yet to get past the "Starting." stage if I was prompted by UAC previously. It does seem that the chance of getting to the 80% mark increases if Etcher has been freshly installed and was launched by the installer, but that is only conjecture. I have not yet gotten the original error on a known-good image, but I haven't gotten to the burn step either, so that doesn't tell us much. None of it is reproducible or consistent, but it's definitely very broken. When I run it as administrator manually, I get this:Īfter reinstalling just now, I got this (which is again covered by #552): ![]() It got past the "Starting." issue once after reinstalling Etcher (using the original image that I linked to), then started failing with various other errors which I believe there are already issues for. Trying again, it happened another 4 times on that image and is continuing to happen on the original image as well. I tried burning an image file that I know has worked with Etcher before, but I hit that "Starting." bug 5 times in a row and gave up. img.xz.ĭoes this happen only with this image? If so, do you have another USB Drive or SD Card to try burning this exact same image to it, and see if the error still happens? img instead.Īh, unfortunate window placement □ It is a. img.xz, but in the screenshot, I see an uncompressed. Obviously, regardless of its validity, the burner should never throw these errors if it can be helped.Īlso, you mention a. The purpose of burning these images is to test this new nightly build system, so it is possible that the image is invalid keep that in mind. Can you share a link to that exact same image you're trying to flash to see if I can reproduce?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |