Sorry didn't see them first. Lol. The cool thing is situations like this remind us sometimes, that a little intellectual curiousity is a good thing. I've seen many on here write about using UUPDump to create iso files, but never really read up on it. Now I've done it, that's a slick little tool to have in the arsenal. Glad for the suggestions from kado897 and IronZorg89. Cheers!
I find that you'll often need to select to not check for updates when doing the upgrade install with the ISO file.
Upgrade to Windows 10
Last edited by Brink; 08 Jul 2019 at 15:28.
I can definitely relate to that and confirm that is so true. The first time I tried it letting Windows check for updates, it took the whole day (not kidding) rolling the little dotted circle to check for updates. At one point I had to close everything and reboot the machine. On second try, I didn't let it check for Updates and everything went without a hitch.
@smactilactus,
Don't forget to mount your .iso after it has been created by the UUPDump procedure. You probably knew that already, but always worth mentioning.
As everyone else here as said, skip the updates check - no real reason for it, particularly with our Insider builds.
Also, not sure if you read back or not, but UUPDUMP just started doing something new , in that they have multiple releases of the same build, which you'll see as Windows 10 Insider Preview 18932.1000 (rs_prerelease) amd64, Windows 10 Insider Preview 18932.1000 (rs_prerelease) (2) amd64, and Windows 10 Insider Preview 18932.1000 (rs_prerelease) (3) amd64, for example, for the 18932 x64 builds. If you're on Skip Ahead builds, you'll want (3) for the updated release, and the one with no numbers for the original release (though there is probably a reason that M$ re-issued it, so you're *probably* better with (3). If you're not on Skip Ahead, but regular Fast track on Insiders builds, you'll want (2).
And since you ran the .ISO, and we're at the same installing screen, I'm guessing that means you mounted the .ISO and ran setup.exe, right?
Yeah, I did. I figured all that out about ten minutes after I left the last message. Went away for a while to do some things on my car, and came back to the same screen, so killed it. Started again, and killed the updates part. And then of course it loaded the new build without a problem. But thanks to everyone for the responses. I appreciate it. I ended up having to upgrade both of my dual boot partitions, as neither of them would do it through WU. So I just finished everything, and all is working well now.
Tumbleweed made it early this morning, but saw that last night for Kernel PPA and decided to switch to Germany. At the same time our forum was dead.
Code:rpm-qa | grep -i kernel kernel-default-5.2.0-1.1.gb36439f.x86_64 kernel-macros-5.2.0-1.1.gb36439f.noarch kernel-default-devel-5.2.0-1.1.gb36439f.x86_64 kernel-firmware-20190618-267.1.noarch kernel-syms-5.2.0-1.1.gb36439f.x86_64 kernel-devel-5.2.0-1.1.gb36439f.noarch kernel-source-5.2.0-1.1.gb36439f.noarch patterns-devel-base-devel_kernel-20170319-8.4.x86_64
Kernel 5.3 RC-1 will be out on July 21st.
Realtek pulled a new Network driver in Kernel 5.2 (rtwpci). WIFI is at best since then.
Note: Always do a clean install with no Internet, same when upgrading from ISO or setup.exe.Code:/sbin/lspci -nnk | grep -iA3 net 02:00.0 Ethernetcontroller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411PC I Express Gigabit Ethernet Controller [10ec:8168] (rev 10) Subsystem: LenovoDevice [17aa:506f] Kernel driver in use: r8169 Kernel modules: r8169 --04:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g /n/ac WiFi adapter [10ec:b822]Subsystem: Lenovo Device [17aa:b024] Kernel driver in use: rtw_pci Kernel modules: rtwpci
Hey #WindowsInsiders, we have released the ISOs for 20H1 Build 18932:
Download Windows 10 ISO File
Tweet
— Twitter API (@user) View on Twitter
Interesting - this is rare. I wonder why?Hey #WindowsInsiders, we have released the ISOs for 20H1 Build 18932:
Tweet
— Twitter API (@user) View on Twitter
Quote
