The HDD will be the bottleneck here. The Win 10 MCT still downloads 19044.1288: Code: <FileName>19044.1288.211006-0501.21h2_release_svc_refresh_CLIENTCHINA_RET_x86FRE_zh-cn.esd</FileName>
By that logic it qualifies yourself too. Did a little digging on the 0x8000ffff, seems to be a plethora of possible causes. Also as Enthousiast noted the HDD is the likely (probable) bottleneck. Highly recommend switching to an SSD, they're relatively inexpensive these days & the difference is night/day. Good luck.
I have a minor bug on 19044.1862. If I manually search for updates and security updates are installed, Windows updates will search for updates again and never finish. If I close the window and check again it finishes quickly reporting not new updates. I am seeing this odd behavior on 4 different systems now.
The thing in bold is my main concern. I did all sorts of suggestions, even ones that suggested stopping windows update and bits and emptying the softwaredistribuition folder, but still no luck. In fact, it did not let me stop bits or even rename software distribution because both were shown as "used at the moment". The main problem that started my forementioned... adventure is an epson printer that was no longer identified by the os as a printer but as a weird (and not unknown) device. The obvious solution to this is to remove the printer and readd it, but it did not change a thing all those 15-20 times that I tried it. The second most obvious is to install some new drivers for it, but this is what gives the 0x8000ffff error when the installation reaches its last step. Searching here and there for solutions to the error gives mostly answers related to the windows update, so I let windows update do any update it had, but it only had July's update to do. After 4 tries that all led to bsods right before login and then to rollbacks, the 5th one was successful and now the system is on .1826. But the printer issue is still there, along with the 0x8000fff error. I even contancted epson's support and they connected via teamviewer and tried the same, but with no different outcome. In fact, the tech guy also tried to install the driver for his epson printer, which was totally different than the one I had available, but windows gave the same error. The above issue was discovered randomly because the user had to print some stuff by yesterday afternoon. On a printer that was bought and installed 1.5 months ago that is. And that has worked with no issues since then. And on which the cell phone and a borrowed laptop print with no issues at all, so the issue is definitely the os on the pc. So, leaving the updates and their reboots and bsods aside, having an ssd on that system would only cut down the time for all the troubleshooting. Sadly, it is a system that ran w7 and was manually upgraded to w10 ~1 year ago by some idiot who thinks every pc is capable of w10 (and who also thinks ccleaner is a great app). Last but not least, no matter how low the price of a small (120gb) ssd is, it is still an issue for the user in question, because, as she said, she can not spend more than 20E for a new pc part, because her finances are very limited.
I tried it just now, but nothing changed. I also tried dism like so Code: dism.exe /Online /Cleanup-image /Restorehealth but still no luck. As for the bsods, I checked with bluescreenview if there was any bsod before July's update, but there was none.
Deploying Dism in this context is ineffective unless the following prerequisites are observed: 1. Ensure that Windows Update service is running. Run services.msc and check the service. 2. Ensure that you are connected to the internet. In this context, Dism contacts an MSFT endpoint to repair your Windows 10 image. 3. Run Sfc /scannow AFTER the Dism command. Sfc will make the repairs, if necessary. In spite of all this, a BSOD (with an error) is often caused by a bad driver or bios setting. First try booting into safe mode. If it boots successfully, with no errors, this could point to a bad driver (like the Epson driver). Also, there could be a BIOS setting that needs to be changed. BIOS settings, like "switchable graphics", can be troublesome.
@jim_p, your printer seems to no longer be compatible with modern windows 10/11, and the chances of it receiving driver updates from Epson to fix it are very slim. (why it worked before and now it does not? because a huge security issue was discovered these last months so microsoft fixed it how they do best - by disabling support) You can reinstall your current version with Media Creation Tool (it will override the build with the older esd one) and then pause updates - it should work again until you resume and WU gets the LCU. If that's the case, best bet is to use an older windows 10 with extended support such as LTSB 2015 / LTSB 2016. LTSC 2019 might also work, microsoft does not backport all the fixes.
@donmiller All 3 prequisites that you mentioned for dism, including the sfc run afterwards, were true when it was run. I am 99.9% sure that wu was running and 100% sure about the other 2. @AveYo How did you come up to this conclusion? I did not mention its model at all, yet you said it is no longer supported. You even said that it has a high security isse that epson won't fix without posting a relevant link to that! If it was such an issue, wouldn't epson's support tell me? Also, you ignored the part that another laptop, running w10 (not an ltsc/b version obviously, because it was bought with w10 preinstalled) does detect and work with the forementioned printer with no issues. Testing on that system will resume next week (August 1st) that the owner will have a couple of days off from work. Until then, anything that can be done, will be done remotely via anydesk and within an ~1 hour window, because that little break is what her everyday tasks allow her. I repeat that the system was misused by someone who has bad knowledge* of apps and windows, so the error windows now pop is definitely his fault. Also, there is no bsod now, just the error when trying to install epson's driver. And because the printer is of major importance right now because she has to print documents weekly, that small problem with the error code (because it does not affect any other aspect of windows), is a major one for her. * Which sane person would upgrade a flawlessly running w7 home installation, on an hdd, to w10 pro, from a bussiness iso, and install all sorts of trash like openoffice, ccleaner, some of iobit's garbage and even put his google account on chrome, syncing everything (garbage bookmarks and useless extensions) to it.
#1 don't follow blindly any random suggestion, say dism has little to do with you, if I understood correctly you just did an in place upgrade, hence your image is ok "by design". #2 when dealing with printers, especially modern ones, removing it from the printer CPL (and/or the device manager) may be not enough. First remove it with its own setup program(s) from the control panel, then check the printer CPL, then go to the device manager, SHOW THE HIDDEN DEVICES, and remove any printer related leftover, double check the grayed out devices in the USB branch, if the printer is connected via USB. #3 once everything is removed, reboot and start, installing the printer using the add printer wizard. Nowadays WU has an huge printer driver collection. Only if WU is not helpful use the epson setup #4 regarding your 0x8000ffff error, the firtst thing you should do to bisect the problem is: launch msconfig, disable any NON MS service, open the task manager and disable any autostarted app. Reboot and check if the problem is fixed, if it's fixed re-enable one by one the things you have disabled (and reboot each time) until you face the error again, then the culprit should became self explanatory.
1) I agree on that. However, I can not know if the iso that did the upgrade was a proper one. 2) The printer is not listed even under printui (google "printui /s /t2" if you want to learn more)! However, all sorts of other printers are still in there, like the fax, the one from office's onenote, even an hp one she had until 2 years ago! I also checked for hidden devices on device manager and found nothing, but I will check again. 3) The add printer wizard does find the printer instantly but takes minutes to install it. As I said above, the progress bar remains stuck at 90+% for minutes each time. Once it is done, the installed printer is not identified as a printer. I did that procedure 15+ times on Friday. On the other hand, epson's driver and its bundled app has a mini wizard that completes in less than 30 seconds, but pops the error. Without that app I would not even see the error! 4) This is something that can not be done remotely and in that 1 hour window that she has available and will definitely be done next time. ---edit Update on the above. 2) There is not a single printer in the device manager, not even as a hidden device. 4) Removing every single non ms service from msconfig and any autostarted app from the task manager had no impact at all to any of the procedures. In fact, all services in there were either from google (for chrome), or adobe (for photoshop), or nvidia (drivers) or teamviewer or anydesk. Nothing more, nothing less and nothing suspicious. 4.5) Making a new account with administrator rights and trying again also had no results on any of the forementioned procedures. So now there is only one thing left, the in-place upgrade that will keep all files. It will be tried next week.
If windows allowed you too keep all files AND SETTINGS/APPLICATIONS the ISO is OK. You don't need the latest one, you need a ISO which has the same MAJOR number, the minor number is not relevant. Say you CAN in place "upgrade" windows (hypothetical) build 12345.999 using the ISO 12345.1 (and any ISO in between), then Windows update will re-upgrade it to 12345.999 or later assuming a new monthly update was released in the meantime. You CAN'T do an in place upgrade starting from (hypothetical) build 12345.999 and trying to use the ISO 10123.10101, because that is a downgrade, like trying to "upgrade" win 98 to win 95. That said a problem during the procedure can't be ruled out, repeating the in place upgrade could make sense, just to be sure. It can take a lot of time if the apps installed are a lot, but the procedure requires no user interaction. So I suggest, eventually, to launch the procedure before going to sleep, in the morning you have your refreshed OS with almost zero fatigue/wasted time. I don't suggest this path, If you care about the user profile. Instead you can install a parallel fresh system in a separate partition (or even better in a native VHDX), then dual boot to it and check if the printer works. If the printer works you can do what you said. If the printer does not work, even on a fresh and clean install, would be pointless to loose the profile w/o fixing the problem (on the original installation). At that point would be better to use an older W10 release, like LTSB 2016. You will loose the old profile, but the eventual incompatibility will be fixed for sure.
Where can I find hash for pl-pl_windows_10_multi_editions_version_21h2_updated_july_2022_x64_4009587d.iso ?