Current Status of Windows 10 October 2018 Update version 1809
-
Yes, that's my normal practice - download once, use many times. In my case I make the x86+x64 ISO as I have both types of install to upgrade. BTW, you can easily make a bootable USB from the ISO should you ever need one. Just format the USB as Fat32, mark the partition as Active (needed for Legacy boot) then mount the ISO and copy everything to the USB.
Thanks Bree, I presume that's what MS expect us to do but if one is simply upgrading from (say) 1803 to 1809 then I'm hoping not to NEED to do it.
I do have an old 32Bit laptop but it can stay on 1803 for now - it's only use is as a music "server" - it might even wait until after whatever the Spring 2019 update turns out to be......if....when the nightmare starts again....
-
- it might even wait until after whatever the Spring 2019 update turns out to be......if....when the nightmare starts again....

Or if..... when..... the current (1809) nightmare ends.
I have clean installed 1809 from the iso and still have problems with
- A non-working Adobe pdf creator from Word 2016, (Excel, PowerPoint work perfectly) and
- A LaserJet service which goes bananas 3-4 times a day!
-
.You meant February 12, 2019. Patch Tuesday is on the second Tuesday of every month, I suppose the new year's eve celebration is still going on. LOL

Absotively! Celebration not ongoing, but the hangover from the cheap champagne clouding vision of the calendar.
-
-
...BTW, you can easily make a bootable USB from the ISO should you ever need one. Just format the USB as Fat32, mark the partition as Active (needed for Legacy boot) then mount the ISO and copy everything to the USB.
Rufus will do all this for you if you have the iso file.
FAT32 requirement is an internet myth...
Scroll down to this section in the link below.
Blah UEFI Blah FAT32, therefore Rufus should Blah
https://github.com/pbatard/rufus/wiki/FAQ
-
Rufus will do all this for you if you have the iso file.
FAT32 requirement is an internet myth...
...
Blah UEFI Blah FAT32, therefore Rufus should Blah
Fat32 with an Active partition is an absolute requirement if you want boot on a legacy system. UEFI can boot from anything, a legacy BIOS can't.
Yes, rufus can create a usb from an ISO, but why go to the trouble of using 3rd-party software to do something that can easily be done without the added complications? A usb created as I described is identical to the usb that the MCT would create. It will boot on anything, UEFI or Legacy.
As @NavyLCDR says...
NavyLCDR said:
If you don't set the all the options exactly the correct way, and set them in the exactly correct order in Rufus you are likely to get a USB flash drive that won't do what you want it to do. I won't recommend that anyone use Rufus.
Can't boot to USB ASUS laptop, despite following recommendations - Windows 10 Forums
-
-
-
Or if..... when..... the current (1809) nightmare ends.
I have clean installed 1809 from the iso and still have problems with
- A LaserJet service which goes bananas 3-4 times a day!
Please tell me...
1) What LaserJet Model do you have and did it work fine under 1803?
2) Have you tried cleanly uninstalling and reinstalling the drivers from the HP Support website? (Image your system first!)
I had a tough time with the 1809 feature upgrade and my HP OfficeJet 8610 until Microsoft rolled out a revised 1809.
-
Please tell me...
1) What LaserJet Model do you have and did it work fine under 1803?
2) Have you tried cleanly uninstalling and reinstalling the drivers from the HP Support website? (Image your system first!)
I had a tough time with the 1809 feature upgrade and my HP OfficeJet 8610 until Microsoft rolled out a revised 1809.

Happy New Year and thanks for the suggestion. 
HP Color LaserJet Pro MFP M177fw, connected via WiFi.
Driver Full package, version 15.0.16259.1230/Sep 28, 2016 (the latest available from hp)
Firmware, updated to the latest version 20180208.
It was working perfectly in 1803, with no errors.
The printer software was installed on a clean-install of 1803 of Dec. 14, which was upgraded to 1809 17763.195, via WU.
As I was imaging after installation of each new software component, the problem is that the images I have are:
1. Clean install 1803
2. Clean install 1803 + hp printer SW
3. Clean install 1803 + hp printer SW, updated to 1809.
Today, as the holiday season ended, I will try a clean install of 1809, from the ISO and see how it goes.
To be honest, I'll do it as I'm more concerned about my second problem in 1809, which was working in 1803, i.e. the inability to save any new file in Word 2016 when the Acrobat 2017 Pro PDFMaker is enabled in Word. And when I say enabled, I mean that the addIn is enabled in Word, as it is in all other Office apps, all its features in the Acrobat tab are disabled, thus unusable, (God knows why) and moreover it does not allow Word to save any file type. If I disable the addin in Word, at least I can save. A problem that neither Adobe, nor Microsoft give any answers, anywhere!
-
Hi again.
I would download the latest iso available with 1809, check for and install any updates and just install the HP software.
I'm glad that you imaged the way you did, so a re-image won't be an issue! 
Let me know if that works.
As for the Abobe problem, I would need to visualize it for myself, since I don't use Acrobat 2017 Pro PDFMaker.
I would suggest posting this question in the Software and Apps section of the forum.
Cheers!
-
IIRC, MS stated there would not be any CUs or FUs issued until after the holidays. I think it was stated this was due to personnel being away on vacations/holidays, so staffing would not support the updating process. I wasn't expecting WU to do anything until next Tuesday at the earliest. The next real "patch Tuesday" might not occur until February 5th, 2019.
Huh? MS said they again started again rolling out 1809 a while ago. Why would they stop it for the holidays? And even if they did what does patch Tuesday have to do with the 1809 update?
I have yet to receive 1809 on five computers. Its clear MS has no idea what they are doing. It shouldn't take this long to issue an OS update. And no there is nothing preventing my computers from getting it.