Hi Jason,
My install was on Hyper-V which started at 7:00amNZT not only bounced while installing but the download bounced as well and finally installed at 9:51
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi Jason,
My install was on Hyper-V which started at 7:00amNZT not only bounced while installing but the download bounced as well and finally installed at 9:51
Canary updated with no issues. Didn't watch it all, but online part seemed long, but offline portion was pretty quick.
Second desktop update with ISO from 25314 to 25324 completed.
Edition Windows 11 Pro Insider Preview
Version 22H2
Installed on 3/23/2023
OS build 25324.1000
Experience Windows Feature Experience Pack 1000.25324.1000.0
We're keeping a close eye on the "bouncing downloads" scenario.
It's has been seen previously when there was a high number of downloads hitting the server simultaneously. There was a big influx this morning from the Canary Channel release, but the number of users hitting this scenario seems to have subsided.
If folks are still hitting this, please do post up here or have them file feedback. We're digging into a few submissions already to see if it was a particular file or server endpoint that was common among those experiencing this.
I had one bounce earlier using Windows Update.
Now I just tried an update from 25314.1010 to 25324.1000 using the MS ISO file just downloaded.
It took quite a long time just checking for updates before finally taking off.
Now it is finally Installing.
We're keeping a close eye on the "bouncing downloads" scenario.
It's has been seen previously when there was a high number of downloads hitting the server simultaneously. There was a big influx this morning from the Canary Channel release, but the number of users hitting this scenario seems to have subsided.
If folks are still hitting this, please do post up here or have them file feedback. We're digging into a few submissions already to see if it was a particular file or server endpoint that was common among those experiencing this.