nukecad

Well it got as far as the restart and said it could take another 90mins. So I got fed up, came to the pub and left it doing it's thing.

The manual update is now available and working (only a day late which isn't bad for Microsoft). See this post for a link and download instructions: https://forum.piriform.com/index.php?showtopic=48074&p=282272

The new version of the Windows Update Assistant is now available of the offical MS website. (It's digitial signature is 04 April). https://www.microsoft.com/en-us/software-download/windows10 If you already have WUA on your computer you may want to uninstall it before downloading the new one (I did). Click on the "Update Now" to download the Assistant and then double click on the downloaded "Windows10Upgrade9252.exe" It should tell you that you do not have the lastest build of Win 10, and that you can update to Build 15063 (which is the Creators Update) - and away you go. I'm running it right now, but with my wifi maxing out at 7.2 Mbps it's going to take a while to download the update.

Just to report that the original problem with Defender Definitions failing in Automatic Updates has now cured itself. (Or rather MS released a fix a couple of hours ago). I just noticed it going through as I was sat doing something else.

Cheers, I'm still not decided yet whether to install it now or wait for the Automatic update. As some have noted on that link you gave, if you are thinking of installing it early then you need the new version of the Update Assistant from Softpedia: LINK REMOVED see post #15 below (This version was briefly on the official MS site but was later removed again, its supposed to be going back on the official site later today). I'll probably leave it for now and think again tomorrow. If I was that bothered about geting updates early I would have joined the insider ring.

Thanks hazelnut, I'm definitely now of the opinion that this is to do with the Creators Update and will probably sort itself after that. I'm just deciding whether to wait till next week for the Automatic Update, or whether to go get it today via the Update Assistant.

For some reason the Windows 10 Cumulative Update keeps killing wifi for some users, different users each time. Last December they managed to knock millions of users in Europe off line. http://www.bbc.co.uk/news/technology-38301548 Microsofts response to that one- issue a new update, which of course the affected users couldn't get because they had no connection. There again a few weeks ago I cleaned up a friends laptop and found it had not had any Windows Updates since she bought it, it still had version 1511. I eventually worked out that is was AVG free that had been completely blocking Win 10 Automatic Updates. Again it's a strange one, AVG will block Win 10 automatic updates on some supposedly 'identical' PCs but not on all.

Thanks everybody for all your input. It probably wouldn't even be noticeable if Defender didn't put out definition updates a couple of times everyday. (Which of course is a GOOD thing and shows they are trying to keep on top of new malware). Like I say I'm pretty sure this is all to do with the forthcoming creators update so I'm just going to ignore it for now. Hazelnut, That's interesting to see, at least it shows I'm not the only one seeing problems with Defender definition updates at the moment, When I update definitions from within defender itself it works fine, it's just the automatic Windows updates that are failing. I do note that the posters on that thread are in the USA. Maybe MS are doing different things on different servers?

TBH the Creators Update is only a week or so off so the OS is going to get a major update anyway. I'm just going to ignore it until then and manually update the Defender definitions from within defender itself. If the Creators Update doesn't fix it by itself then I'll probably download the ISO and do a complete reinstall from media. Looking online this has been a recurring problem with Defender definition updates for years now. I'm still guessing that this time it's to do with the Creators Update preparations. I know that part of this update is going to be big changes to Defender and the Windows Security Centre, maybe they have installed/changed some component before they should have.

For the last 3 days Windows Defender Definition Updates (through Automatic Updates) have all failed with the error message: "Definition Update for Windows Defender - KB2267602 (Definition 1.239.688.0) - Error 0x80070643" Launching the Defender UI and updating definitions from there does work OK. I haven't made any changes to the system, but I have noticed that Windows itself is running scans and creating various 'Compatability" and other logs this week. Presumably it is doing this to prepare for the Creators Update due next week. With Windows 10 Defender is part of the OS and so you can't uninstall/reinstall to try and repair errors. What I've tried up to now- Turned of all other real time malware protection except defender (MBAM v2, MBAE v1.09). Update still fails. Run sfc/scannow from an elevated command prompt. (no issues found). Windows update problems can often be related to NET framework, so: Run the NET framework repair tool from MS. (Said it found issues but couldn't resolve them, automatically sent logs to MS). Obviously various reboots and restarts during all this. Rebooted in Safe mode with Networking. Couldn't even get to Windows updates in the settings, the settings screen just closes itself when tried. I may try a restore point next, or may not. If it is something MS have snafu'd in the lead up to the Creators Update then it'll just do it again after the restore. It's no biggie, but I just wondered if anyone else is seeing this problem?

Did you totally clean out Chrome from your computer? Just Uninstalling it is not enough on it's own, Chrome is very persistent and uninstalling it still leaves files, folders, and registry entries behind It could be that Ccleaner is seeing these old folders or reg entries. Take a look at this video guide to getting rid of Chrome completely:

I still think the Google TiSP was the best one. I hear that they are going to start doing fibre broadband in the UK this year. TiSP2?

You guys have realised what date it is today?

52.0.2 has been released. https://www.mozilla.org/en-US/firefox/52.0.2/releasenotes/

Careful, you don't want a spider bite on your thingy.

"Complete" cleaning simply means that the pro version can clean up all user accounts on a PC at once when run from an admin account The free version only cleans up the one user account that it is run from. (So if there is more than one user account on your PC then you would need to run it seperately from each user account to clean that account). There is no difference to the cleaning process itself, just which user account(s) it can clean at a time. Many people agree that "Complete Cleaning" is not the best term that could have been used for this function. "All Account Cleaning" may have been a better choice.

It may be something to do with the new login warnings with FFx 52 https://support.mozilla.org/t5/Protect-your-privacy/Insecure-password-warning-in-Firefox/ta-p/27861 But just to be sure first, have you unticked 'Saved passwords' in the Firefox section of CCleaner?

To paraphrase a couple of quotes - "We did it because it was there to be done" "Just because you can do something doesn't mean you should do it"

If it's saying 100% defragmented then there is nothing to be defragged so what action were you expecting? The System Reserved Partition doesn't need defragging - it does not affect system performance in the slightest. It is a very small partition that contains boot information, once you are booted it does not affect anything else. http://windowssecrets.com/forums/showthread.php/174296-quot-System-Reserved-quot-partition-won-t-defragment I'm not sure if you can normally defrag the System Reserved Partition anyway, because it does not normally have a drive letter. You may need to give it a drive letter before you can (try to) defrag it. http://www.thewindowsclub.com/system-reserved-partition-windows If you realy want to try then you could try doing a boot time defrag first. (I've used this in the past to defrag the pagefile and other system files that don't normally get defragged because they are in use by Windows). Because this runs before Windows is initialised it can defrag the files that Windows itself uses and are nornally locked from defragging. In Defraggler go to 'Settings' and select 'Boot time Defrag' from the menu. ('Run Once' should give you an idea if it will defrag the System Reserved partition). Then shutdown and reboot your computer. Check to see if the partition has been defragged. But you say that yours is already 100% defragmented, so I don't know what difference you would see anyway?

This Password warning/blocking behavour will not change. (The warning message/pop-up itself may change slightly, and the vBulletin HTTPS issue may be fixed). But overall this warning/blocking is an intended feature and not a bug, so as far as Mozilla are concerned there is nothing to be 'fixed' and it will remain.

There is a checkbox during the download procedure. It is pre-ticked and you have to untick it, maybe not ideal but that's the way the world works these days. Lots of downloads offer additional software. It's up to you to check every stage before you click the 'continue', 'next', or 'OK' buttons. If you don't see the checkbox for Chrome then that is probably because you already have some Chrome components or references somewhere on your computer. These could be 'hidden' in the registry or elsewhere. If you do already have these then you will not be offered Chrome again as the downloader thinks you already have it.

Good to hear that I'm not the only one who saw this as a problem, and great that toggling the setting worked for you as well. My real beef was that Mozilla pushed this out without any warning to users who are not in their insider/development/beta club. They didn't even mention it in the original release notes. They have added it now but it still doesn't say that it will totally block some logins, just that it will display a warning PS. you might want to change you Firefox update settings to 'Check for updates' instead of 'Automatically install updates'. PPS. That one where it had seemed to change the password at the forum gets even stranger. The password had not been changed at all, but for some reason Firefox wouldn't let me login there until I changed the password and changed it back again. Guess we'll never track down what caused that, and will just chalk it up as a WTF?

Always good advice. But we are pretty sure that this was not from a third party, and that it is something that Mozilla did in the update. Finding evidence of that is a different question. No way am I trying to call mozilla names for this. (Unless we can find evidence). Obviously we have stopped Mod (and all other) privileges on that account and are keeping an eye on any future login attempts. Just a bit of a pain when you have 12 years plus posts from the account.

I got it direct from Mozilla, when Firefox came up with the usual upgrade popup and I clicked on the 'Upgrade Now' button. Like I said above I've got the autofill of usernames and passwords in forms working now by going to about:config and toggling 'signon.autofillForms.http' from false to true. The actual warning notice itself and the blocking seem to be controlled by 'security.insecure_field_warning.contextual.enabled' and 'security.insecure_password.ui.enabled'. However if I toggle these to false to get rid of the warnings then logins are blocked altogether. (I suspect that this is intentional- either warning or blocked altgether). Even odder- The one site that I reported as still being blocked seems to have had had the password changed at the forum itself. Once I did the 'Forgotten Password' thing to get a new password I was able to login to it with that new password, and to change it back to my previous, saved password. It now logs in from Firefox with that previously saved password again. This is a bit incredible to say the least and I'm not sure just how Firefox could even have done that. I am still investigating that one with the forum administrator there, he should be able to retrieve any password changes made to check if Firefox did somehow manage to change the password. I certainly hadn't. I suspect though that it is something deeper, I should also have not been able to reset it to a previously used password, the forum software will not allow that. (I mod there, so I login to that site 2 or 3 times daily using the password saved in Firefox some time ago).

Well I've now fiddled with the Firefox config. settings and got the auto filling of login forms working again for all my vBulletin and Xenforo sites except one. That one may be doing something slightly different because it is the one where I am a Super Moderator. I'm still getting the warnings but I can live with that for now. I tried turning them off in config. but that just blocked logins altogether again. And yes I have sent some snotty feedback to mozilla.