FYI, two of my machines saw that 'download and install' notification within 15 minutes of the official launch on clicking 'check for updates'. There were no prior 'coming soon' or similar notifications. Both successfully updated through Windows Update.
Thanks. Opinion on Google is overwhelmingly saying that a clone drive has no influence on the boot-up cycle. The OS boots from the drive that the BIOS tells it to.
I run a clone of the drive every three months, in addition, at that time, I run an Acronis full backup of the C partition. I have a task scheduled to run an incremental Acronis backup every Saturday. In addition, if I have been making substantial updates to the system any time during the week, I run a further incremental backup at that time. I keep the previous three-month Acronis backup cycle for three months.
So in total, I can revert to any one of many images over a six month period. My backup plan is comprehensive, verging on OCD ;-))) Based on past bad experiences with PCs.
There is light in the darkness over this past week, I have received updates of an Intel driver and some apps, all citing "incompatibility with 2004" as the reason for the update. So with patience come August all might be fixed. I'm going to sit it out.
Thanks for that update. Waiting until August is a good idea.
Post #43 “Opinion on Google is overwhelmingly saying that a clone drive has no influence on the boot-up cycle. The OS boots from the drive that the BIOS tells it to.”
--- No one in this thread disputes that.
In my post #36 “A Feature Update is a different story.
Keep ThrashZone's post #28 in mind even you use the ISO
"Any reason you've never disconnected at least the data cable off the clone ?
Being a clone they would have the exact same id's so maybe this 2004 build is getting confused and aborts ?"
Here is an article on 12 Things You Should Do Before Installing a Windows 10 Feature Update
12 Things You Should Do Before Installing a Windows 10 Feature Update
Update: This post was originally written for Windows 10 1703, but all the steps are still sound and worth double checking before installing any new Windows 10 feature update.
--- One of the recommendations is “Disable Peripherals and External USB Devices”.
On "Failure code is... 0x80242016 WU_E_UH_POSTREBOOTUNEXPECTEDSTATE" in post #40.
--- Reliable sources to address it are being researched.
From your link I obtained this cmd... rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN
...but it appeared to do nothing.
Please don't be insulted if this is obvious to you: All 3 of my laptops would not take 2004 successfully until I set Malwarebytes to NOT start with Windows. Even though you probably only use Malwarebytes on demand, are you sure it is not running resident in the hidden system tray?
Curious what kind of problem you had that you traced to MBAM. Did it specifically give you an error that referenced MBAM?
At least three of my computer installed 2004 just fine with MBAM installed. I had never disabled MBAM previously and updates always installed. For the one computer I am having difficulty with I disabled MBAM and it made no difference.
You know, there was an error code thrown that pointed me to shut MBAM off but, for the life of me, I can't recall and didn't record what it was. In post #23, the language "Failure code is... 0x80242016 WU_E_UH_POSTREBOOTUNEXPECTEDSTATE" was something that vaguely rang a bell and may have been part of what prompted me to shut off MBAM. But I did have 3 laptops (two Dells and an HP) fail on first attempt and then succeed with MBAM unloaded.
Sorry I couldn't be more clear about that. FWIW, I too have never had to disable MBAM for any update, including feature updates, until now.
Malwarebytes does not run on my PC unless I invoke it, it certainly does not run in the background at any time.
Hi,
I mounted an iso on x299 it has mbam pro full protection and no issues completing the 2004 install.
Quote
