Dave-H

Thanks, that's interesting that you're seeing the same thing on a clean install! I suspect the notice appeared on mine after the first update was applied, which was a Flash Player update. It definitely wasn't there straight away. I'm just interested to know if everyone is seeing this, and what exactly is supposedly being "hidden" on the page! I am of course an administrator on the system, so I can't imagine why anything would be hidden or disabled on Windows Update. Searching online about this brings up virtually nothing, the only other references to that notice seem to apply to the customisation page where you change things like the lock screen image, where it appears if you have things disabled using Group Policy settings. I couldn't find any references to it appearing on the Windows Update page.

I recently updated Windows 10 to version 1703, the so-called "Creators Update", and everything seemed to go fine. However, a strange thing has suddenly appeared on my Windows Update settings page. At the top, it now says, in red, "*Some settings are hidden or managed by your organisation". This was not there straight after the update, it suddenly appeared a while later, and I haven't knowingly changed anything that would have made it appear. It's also there on the page if I click on "Advanced options", but nowhere else. Anyone any idea what is actually hidden or disabled here, and why? I'm using Windows 10 Pro 64bit.

Yes Heinoganda is brilliant, his updating program for the Root Certificates alone is amazing!

Good news! How did you actually get the updates to install? Did you use @heinoganda's roll-up version, and did you do it normally or using the Recovery Console?

@SD73 I've never had any luck either with System Restore on one of my XP machines. Every time I've tried to use it, on any restore point, it goes through the motions and then just says "the system could not be restored" without giving any reason. Your problem is certainly a very strange one. My only thought, and it's clutching at straws, is would it perhaps be possible to try installing the updates with the standalone installer files when booted into the Recovery Console? I have no idea whether they will even work in that environment, but just a thought.

Indeed so, but KB40414580 is an update specifically for .NET 2.0 SP2, as can be seen from its standalone file name. One strange anomaly was that on my netbook, but not on my main machine, after I successfully installed all the updates, I was then prompted to install a further five .NET 2.0 updates, which presumably weren't installed before. They took ages to install, and I was dreading that there would then be another prompt to install KB40414580, and then the five updates again, and so on round and round for ever, but fortunately that doesn't seem to have been the case. Whew!

Just to report all 13 updates installed OK on both my machines. Strangely my main machine never showed a yellow shield in the system tray, whereas my netbook did. It took about 20 minutes to scan with Microsoft Update on my main machine, on the netbook it took a couple of hours! I guess that's because it's a pretty weak machine. The .NET updates took ages to install, but they always seem to.

I never used ClearType when I had a tube monitor of course, but since I've had a flat screen monitor I actually do think it's better, as long as it's correctly tuned of course, which is a very big "if"! Do you have the ClearType Tuner for XP installed? If not, you should give it a try. Even if you still don't like the result, at least you will have made sure that it's as optimised as it can be, because if it isn't, the results can be truly horrendous!

Not a gratuitous bump, although I've just had to completely re-backup all my files again today as the clocks changed, which is what's made me think of this. As well as the already documented here issue of backing up a FAT32 drive to an NTFS drive, I've also noticed another strange thing that I've now confirmed happens when the clocks change. I have a lot of my archive drive folders set to "thumbnail" view mode, for images and video files, and every time the clocks change, all of the thumbnails seem to have to be re-created. Why would that be? This is completely on a FAT32 drive, no NTFS issues. Surely if all the files on the drive have their timestamps changed when the computer clock moves forwards or backwards an hour, by the same amount, why should that cause the thumbnails (stored in the thumbs.db files) to have to all be regenerated?

A noticeable improvement here too, although I must say that I hadn't actually noticed a problem. Thanks!

I had this problem with my dual boot netbook that it would boot fine into Windows 8.1 in AHCI mode, but not into XP. Installing the Intel Application Accelerator fixed it perfectly for me, but I don't know if that was the preferred solution!

The .NET update seems to have installed fine for me with no problems. Scanning the versions of my .NET system files, it seems to have updated quite a few.

I wasn't knowingly pushed with KB4012864, no yellow shield appeared, but just as a test I tried doing a scan on Microsoft Update. Not only did it then appear as a high priority update, so I installed it from there, I was very pleased to find that the scan completed in only about 30 seconds. Whether this will be the same come the next patch Tuesday remains to be seen!

Thanks! Does that .NET update supersede any others, and why does it say it's a "preview"?

The strange thing was that after both my machines had been updated, a further scan on Microsoft Update with IE8 completed very quickly, and of course showed no critical updates available. Whether this means that the issue has been fixed remains to be seen of course!

LOL @ginz, I (and my PC) are fine thanks! I've just successfully updated both my XP installations with all 11 updates, and the Silverlight update. With Flash updates I usually wait now until Firefox tells me the plugin is now too old to use. My God the scans took such a long time though, I do hope they've finally fixed this issue this month, whatever it is! If this was happening with "real" POSReady/WindowsEmbedded installations, as well as hacked XP installations, MS must surely have had a huge number of complaints about it by now.

It won't be shown in the Windows Update list if you installed it manually from the standalone installation file. It should be listed in Add/Remove Programs though. Glad to hear we've actually got some updates this month, I guess we'll never know exactly why all of last months were pulled!

Ah, understood (I think!) So if the Firefox version being declared to the servers is 52.0, which it would be now if you left the variable as "%VERSION%, the plugin will never download as it's not offered on versions above 51, so you have to make sure it always still pretends to be version 51? I guess if you already have the plugin and you're still saying you're version 52, it just means you would never be offered any updates to the plugin, but I presume that's never going to happen now anyway!

Do you still need to do that if you've already got the plugin, or does it not matter in that case?

Yes, that's exactly what I've now got, all -1 hour on the times in the first image due to the time difference between the UK and mainland Western Europe.

Hence the inverted commas in my post!

Disgraceful, if they start putting forced advertisements into an operating system that many people must now have actually have paid for, I will not be pleased, and I will seriously consider "downgrading" as well.

Sorry I'm not sure how to check that. I have just run the updater again though, and my updroots.sst has changed, it's now dated 28/02/17 instead of 12/11/16, which is good, but strangely, my disallowedcert.sst is now dated 24/05/16 instead of 25/05/16 as it was before!

I've now got: authroots.sst 28/02/17 delroots.sst 12/11/16 roots.sst 24/07/15 updroots.sst 12/11/16 disallowedcert.sst 25/05/16 Does that look right? Of course I can't remember what the dates were before, I should have noted them, but authroots.sst seems to be the only obvious new one.

Yes, let's hope there's enough of us on their radar for them to justify keeping 52 ESR at least updated with security patches for another year or two.