Announcing Windows 10 Insider Preview Build 15058 for PC Insider

Edwin said:

I think that's been there for a while; I'm on AU and I have it.

Duh....mind you I did state "not noticed before"
Could this not have been made with the latest updates on AU.?

After trying for 5 times using the Restart Now button, it just wouldn't update to /15058.

- must be related to the deletion of all contents in het > Download folder (?)



Googled for the error. I read on the MS support forum that in this case I just needed to wait and try again, but still a no-go.

Then, after using the Update and Restart option in the power options menu instead of the Update, it finally started the update cycle.



Up-and-running with my VM-WIN10-15058u! The UUP update cycles - all updates from /15019u in just 1 VM - work just fine for me.



Cheers

I got that few times before I gave up and downloaded without UUP. As soon as I switched it off, it started download, of ESD type.

CountMike said:

I got that few times before I gave up and downloaded without UUP. As soon as I switched it off, it started download, of ESD type.

But it was - to my believe - due to my own actions, deleting the contents of the > Download folder that I got this hick-up to begin with. So far all my UUP updates were more or less flawless.

Cheers

M4v3r1ck said:

But it was - to my believe - due to my own actions, deleting the contents of the > Download folder that I got this hick-up to begin with. So far all my UUP updates were more or less flawless.

Cheers

I used Disk Cleanup and believe it removed contents of that folder, after that it downloaded the ESD way.

dencal said:

Noticed a nice little addition in File Explorer, not noticed this before....including Disk Cleanup

Edwin said:

I think that's been there for a while; I'm on AU and I have it.

Edwin said:

Naw, it's been there the whole time, since whenever AU came out anyway.

I never really noticed the above posted by @dencal before either but as @Edwin stated it is available in the AU and is seen only when highlighting the C: drive.

I could have saved myself some trial-and-error time, if only I wouldn't have - in the heat of the moment - overlooked post #37-#40 in this thread.

Cheers