Announcing Windows 10 Insider Preview Build 16237 PC for Fast ring Insider
-
All good here again. Just love boring:)
-
-
16237.1001 installed without any hiccups for me. First time for several builds that there has been no drama. And I had Vipre, Malwarebytes Pro, CryptoPrevent installed and running when the update process started. All my internal drives and peripherals were connected.
I did have .NET 3.5 disabled this time. Maybe that was why this build installed without hiccups?
One of the little programs I use needs that, which reminded me it was disabled.
-
This is frustrating. For the last 5 builds or so, I have been trying to create my own ISOs, but I have failed when I use the UUPtoISO tool by getting a message similar to the one seen below:
My process of creating the ISO goes something like this:
- download the UUP folder through my VM using Windows Update like normal
- Copy the UUP folder to my host computer
- Run UUPtoISO on the UUP folder located on the host computer (not VM, I do this because I think the performance would be significantly degraded if I run UUPtoISO on the VM)
- If ISO created successfully, burn the ISO to my flash drive using Rufus :)
My guess is that somewhere in step 2, in the copying process, some folders aren't getting copied over properly, hence this error. Is that correct?
What can I do to correct this error?
Much thanks TF!
-
It is strange that the new option to limit the bandwidth used by Windows update is not mentioned in the novelties of this build, it can be found in Windows update-Advanced options-Delivery opimization-Advanced options, there is a whole new section to limit the percentage of bandwidth that uses Windows update.
-
-
It is strange that the new option to limit the bandwidth used by Windows update is not mentioned in the novelties of this build, it can be found in Windows update-Advanced options-Delivery opimization-Advanced options, there is a whole new section to limit the percentage of bandwidth that uses Windows update.
Oh wow. That's good to know, because Windows Update has gone a bit psycho on my bandwidth lately. Thanks for pointing this out.
-
This is frustrating. For the last 5 builds or so, I have been trying to create my own ISOs, but I have failed when I use the UUPtoISO tool by getting a message similar to the one seen below:
My process of creating the ISO goes something like this:
- download the UUP folder through my VM using Windows Update like normal
- Copy the UUP folder to my host computer
- Run UUPtoISO on the UUP folder located on the host computer (not VM, I do this because I think the performance would be significantly degraded if I run UUPtoISO on the VM)
- If ISO created successfully, burn the ISO to my flash drive using Rufus :)
If I had known about your workflow earlier when you have told you fail with UUPtoISO, we could have solved your issue a few builds ago.
You can't copy the UUP folder to another computer to make an ISO, you must do it on the machine where upgrade was downloaded, initialized and prepared. Your ISO making will fail when trying to use UUP files from another computer, be it a physical or virtual machine.
You must run UUPtoISO on your virtual machine, then when done copy the ISO to host.
Kari
-
If I had known about your workflow earlier when you have told you fail with UUPtoISO, we could have solved your issue a few builds ago.
You can't copy the UUP folder to another computer to make an ISO, you must do it on the machine where upgrade was downloaded, initialized and prepared. Your ISO making will fail when trying to use UUP files from another computer, be it a physical or virtual machine.
You must run UUPtoISO on your virtual machine, then when done copy the ISO to host.
Kari
If VM is in a .vhd or .vhdx format (hyper-v), you can mount the drive in host - I do that sometimes to run uup as quicker.
-
Oh wow. That's good to know, because Windows Update has gone a bit psycho on my bandwidth lately. Thanks for pointing this out.
Good thing it wasn't enabled by default. Was it there in last (232) update ?
-
Good thing it wasn't enabled by default. Was it there in last (232) update ?
Not sure. I wasn't on 232 very long. First time I've seen it mentioned though.
-
-
This is frustrating. For the last 5 builds or so, I have been trying to create my own ISOs, but I have failed when I use the UUPtoISO tool by getting a message similar to the one seen below:
My process of creating the ISO goes something like this:
- download the UUP folder through my VM using Windows Update like normal
- Copy the UUP folder to my host computer
- Run UUPtoISO on the UUP folder located on the host computer (not VM, I do this because I think the performance would be significantly degraded if I run UUPtoISO on the VM)
- If ISO created successfully, burn the ISO to my flash drive using Rufus :)
My guess is that somewhere in step 2, in the copying process, some folders aren't getting copied over properly, hence this error. Is that correct?
What can I do to correct this error?
Much thanks TF!
Personally, I would just run the uuptoiso per Kari's inside the VM and accept the one time performance hit. Then just copy the iso to your host and burn it or whatever. This has never failed for me (but I have only used a VMware VM - perhaps once a Virtualbox VM).
Actually Kari beat me to the punch and with more information. I almost always follow the developer's advice.
Last edited by martyfelker; 08 Jul 2017 at 03:30.