What can I do to a 21h2 + all updates until June (.1766) installation of w10 pro that refuses to get July's update and goes to bsod on reboot (and rollbacks to the previous one)? I have already tried sfc scannow and a couple of other things I can not remember. I think that this failed update leads some apps to 0x8000ffff error the last couple of days.
Allow me a question because I have a doubt about that in-place "upgrade". I did such an upgrade ~4 months ago, for a similar reason (wu was stuck in an endless download loop and was consuming bw and cpu cycles like mad), but it was more like a "fresh install that lasts a lot longer than a real one but lets you keep your files".
An inplace/repair upgrade should show the option to keep all, files, apps and settings, after it's finished it should all be the same but now in a fresh state and uptodate (when using an uptodate ISO).
Yes, that is what it does. For me, it is the same as the "reset your pc" option from the ones under recovery, with the sole difference that it updates the os to the latest version. If I choose that option, all files will remain intact. But what about the apps? I do not mind reinstalling the browser or the media player, but reinstalling a major app, like photoshop. is a big task.
As I said above, this is like a "fresh install that lasts a lot longer than a real one but lets you keep your files". This means I will have to reinstall all the apps and so on. Right now I am doing my fourth try today to install July's update.
No it does NOT. Had you done the in-place upgrade by correct ISO or "fresh install that lasts a lot longer than a real one" as you described it you'd be up to date with all your apps & settings UNTOUCHED in much less time than many useless attempts at updating an obviously corrupt install. But that's just my .02 cents. YMMV. As Enthousiast, who's much more knowledgeable than I, already noted:
That last time I ran the setup file and asked it to keep all the files (not sure about the apps), it took 4+ hours for that in place upgrade! And fyi, in order to do that, I will need July's iso, which is like 1+ hour of downloading on my end. And all that must now be done by an average user, because I spent my entire morning trying to find a better way than the one you mentioned. Anyway, July's update was successfully installed after that 4th try, but the problem with the 0x8000ffff error remains.
I too am an average user (well maybe slightly above average ) but I'm only trying to be helpful. I'm out.
If I use mct to download a new iso, will that have July's update too? @E_B_M If you are posting on this forum, which means you understand everything that is said, you are above an average user by a lot
It most likely will download the 22000.318 ESD file to create the ISO. Code: <FileName>22000.318.211104-1236.co_release_svc_refresh_CLIENTCHINA_RET_x64FRE_zh-cn.esd</FileName> The amount of time an upgrade will take depends on the hardware, the amount of files to keep and how crazy the AV goes on them.
It's an 6th gen i3, 8gb of ram and an hdd unfortunately and I have left defender to be the av. As for the iso, isn't that version you mention for w11? As it seems, it will not grab an updated iso for 10 too.