Dave-H

I certainly didn't have to do it one file at a time, but I did have to start with the sub-folders and work my way up to the top. If you get the error message, just go one more level down and try deleting the individual folders at that level. As Noel says, make sure that you have the checkmarks ticked to inherit permissions down the chain.

Glad to hear that you fixed it! Interesting that it is working with the new version of the dll.

When I deleted that folder on my friend's machine, I seem to remember that I had to do some of the folders separately, taking ownership of them and their contents and then giving myself full control over them. It was a very tedious process, but I got them all eventually!

Did you replace the dll? You'll still have to do that!

Yes, the Windows Update page will lose its list of updates that you installed in the past, but they should all still appear in Add/Remove Programs so you can still uninstall them, if they can be uninstalled of course, some can't. You will need to have the "show updates" option checked there of course.

Try running the Windows Update Troubleshooter. This will reset everything on Windows Update and might kick it back into life. You may well still have to replace the muweb.dll afterwards.

From my first hand experience with actually doing the update (which I quickly undid!) "ready to install" actually means ready to download and install. I doubt if the files are already on the machine, especially if the C:\$WINDOWS.~BT isn't present. It's around a 2GB download for the upgrade from Windows 8.1, probably more if it's a Windows 7 machine. It's certainly not going to happen suddenly, it took ages when i did it.

You could try the Windows Update Troubleshooter. That does a lot of resetting of Windows Update, and might fix things for you. You will lose your update history.

@Odos270 Do you have a System Restore point available from before this all happened? I used that on a friend's computer to reset Windows Update to working normally again.

Sounds like you're probably OK to reboot in that case. Windows Update may try to start the Windows 10 download routine again, but you should be able to abort it.

Do you have a hidden C:\$WINDOWS.~BT folder on your drive? If so, trash it, as that's where all the Windows 10 installation files are. You will need to take ownership. Once you've done that, Windows 10 should not be able to install even if it tries after the reboot. What state this will leave Windows Update in I don't know I'm afraid.

LOL! I do have to say that after spending a while poking around Windows 10, I was actually quite glad to see Windows 8.1 back again! As with all new operating systems I'm sure it's very much just a matter of getting used to it, but I didn't much like what I saw at first glance. It did seem to have some advantages, for instance they seem to have dropped the annoying restriction that apps won't run unless you have the screen set to at least 768 pixels vertical resolution, something that's a bugbear on my netbook because it only has a 1024x600 screen! I played (very briefly!) with the Cortana search engine, but backed out pretty quick when it said I had to sign in to Windows with a Microsoft Account to use it, and implied that this was permanent and irreversible. No thanks! The only things I lost restoring the backup were my offline files, which I had to completely re-synchronise, and my Windows Update history, which was annoying. Why that isn't preserved in the backup I have no idea.

Well the restore of the System Image Backup was successful I'm very glad to say, and I've now got Windows 8.1 back. It also restored Windows XP of course so I had to reapply a few updates there, but generally no problem. No worry with the licensing either I'm pleased to say. I'll keep an eye on the guys working on a GMA 3600 driver for Windows 8-10 here, and I may have another go if they come up with anything.

I very much doubt if the graphics driver would have been stable even if I had suppressed the TDR crash, but thanks for that reference! I'm now restoring my System Image Backup, so I will see if it does indeed put me back where I was before! Watch this space......

Well sadly I'm now at the point of giving up with Windows 10 on my netbook. As I was warned, the graphics driver is completely incompatible, even more so than with Windows 8.1. It installs fine, and the lock screen and logon screen are fine, but it crashes as soon as it tries to load the desktop (VIDEO_TDR_FAILURE) and try as I might I cannot resolve this. There are people working on a driver for the Intel GMA 3600 for Windows 10, but there's nothing available as yet. It's annoying, because it must be so close to working. If I change to the basic display driver, and then update to the Intel driver while the machine is running, it installs and the display changes to the correct resolution, and it seems fine, but as soon as I reboot it crashes again. Rather annoyingly, I don't have the option in the recovery menu to roll back to Windows 8.1. I did a reset of the machine at one point and told it to remove everything, and that might have removed the option, although the old OS is still there in the Windows.old folder, there seems to be no way now to get back to it from within Windows 10. I'm going to try the backup I've got of the whole system on an external drive, and see if I can restore from that.

Well, it took ages, but I now have Windows 10 Pro on my netbook! Thanks very much again to @NoelC, and the guys at vmware of course! My first reaction is that it's ugly, even compared to Windows 8.1! It's stuck with the Basic Display Driver at the moment though, so I'll reserve judgement on it until after I've (hopefully) got the proper graphics driver installed. I'm getting error messages from Nero telling me that it can't find advrcntr5.dll as well, but I guess that will come good if I reinstall it, assuming that the version I've got is not completely incompatible with Windows 10 of course!

Well, I'm downloading Windows 10 now, so it did work! Thanks again for the link to the fix @NoelC. I have a fairly recent ISO backup of the whole machine, so hopefully I'm covered in case of disaster, but we'll see. Wish me luck!

Thanks @Tripredacus for moving the post. I've edited my first post to remove the parts that were only relevant when it was in the other thread, to avoid confusion. Thanks Noel. much appreciated! I'll have a look at that and see if it's worth trying. Cheers, Dave.

Thanks jaclaz, understood of course. @dencorso, could you do the honours please? I don't know whether this should now go in the Windows 8 or the Windows 10 forum, I'll leave that up to you.

I had decided that I would try the Windows 10 "upgrade" on my small netbook to assess it before deciding whether I wanted it on my main machine. The netbook is dual boot Windows 8.1 Pro and Windows XP Pro. I registered for the upgrade, but nothing had happened as yet, and when I checked today, i was informed that my netbook had been declared incompatible with Windows 10 because there is no Windows 10 graphics driver available for it. The graphics driver presently installed is the Intel Graphics Media Accelerator 3600 Series. Now that doesn't even have a Windows 8 driver available (the machine was designed for Windows 7 only, I had great difficulty even finding a Windows XP compatible graphics driver for it!) but it installed and runs Windows 8.1 absolutely fine, so I've no reason to think that it wouldn't run Windows 10. Very briefly, does anyone know any way or over-riding the compatibility check so I can get the free upgrade? Cheers, Dave.

Yes, both installed with no apparent problems. The latter is only a new version of tzchange.exe (now 5.1.2600.6861) to update daylight saving time start and end dates which have changed in some countries.

Interesting. My friend whose laptop I found had what appeared to be a complete Windows 10 installation downloaded on his hard drive, has never seen the "Upgrade to Windows 10 Home" entry on Windows Update, although it looked to be ready to go! Other Windows Updates do seem to be still installing OK under manual control, I'm glad to say. Slightly off-topic, but I spoke to another friend of mine a day or two ago, who has an elderly Windows XP PC, which has been malfunctioning. He now seemed to be convinced that he "must" have Windows 10. I asked him why he was so keen, after pointing out to him that he wouldn't get a free upgrade from Windows XP, even if his machine would run Windows 10, which is extremely unlikely of course. He replied that he'd seen an item on TV where people were talking about Windows 10, and they were saying that it's the ultimate version of Windows, to the extent that it will be the last version, and there will be no new versions in the future! Supposedly these were spokespeople from Microsoft, which I find rather hard to believe! Anyway my friend now believes that anyone who hasn't got Windows 10 is being left behind, as it is the future, now and forever! So, the propaganda is working, at least on the non-technical gullible!

Indeed, I've manually installed that as well! BTW, does anyone know why the .NET updates aren't being offered by Windows Update, as they always used to be?

Sorry, my mistake. There were indeed five updates for the Office 2007 Compatibility Pack. KB2837610, KB3054888, KB2825645, KB2986254, and KB3054890, as you say. The other OS security updates were KB3078601, KB3076895, and KB3073921. The other two of the total ten were the IE8 Cumulative Update and the Malicious Software Removal Tool.

Just an update on my friend's Windows 7 laptop that I mentioned in post #122. I looked again today at it and found the dreaded hidden C:\$WINDOWS.~BT folder sitting there, with about 5 GB of presumably Windows 10 files in it, just waiting for someone to double click the setup.exe file! It was dated from about ten days ago, and how it downloaded such a huge amount of data in the background without anyone being aware of it is rather worrying, as even though the machine is on a connection that's fast for ADSL, it would still have taken hours to download that amount. Needless to say, after tediously wading through all the necessary permissions changes, it was consigned to the recycle bin!