Dave-H

I certainly hope that doesn't happen, in case I want to roll back to 8.1, but they could argue that by accepting a free upgrade you have abnegated your previous licence.

The last time they messed an update up like this the update would only install on US English systems. This update does install on my UK English machine (just for information, no help to you I realise!)

All four offered updates installed fine here. No ill effects noticed so far!

A friend of mine has a Windows 7 Home Premium laptop, and he's had the "Get Windows 10" icon appear in his system tray. He asked me "do I want Windows 10" and I told him to wait until I'd tried it! I'm used to Windows 8/8.1 so it won't be such a shock to me as it will be for him who's used to the Windows 7 GUI. I've registered an interest in the Windows 10 "upgrade" on both my netbook and my main machine. I'll try it on my netbook first, which is very under-powered, as apparently from what I've read Windows 10 has efficiency improvements that should help on less powerful machines. I'll be doing a full ISO backup first of course so I can hopefully roll back to 8.1 if necessary!

Had a reply here. Looks like it may be a more general problem.

Thanks, I suspect that confirms it. I have posted to the two MS forum threads I asked about this on last year. Hopefully we can get clarification as to whether this facility is now officially dead.

Well I finally came around to the conclusion that it was the name "Archive" for the shared folder on the server that it didn't like. Not because there's anything wrong with it as a name of course, but possibly because I had been syncing using the same share name (of course) on all three of my server's operating systems. I think what may have happened is that something got corrupted on the Windows 8.1 client, possibly character cases or something, which resulted in the client no longer being happy with the share root name on Windows 8.1. I had noticed that depending on which machine I looked on, and on which OS, it was sometimes "Archive", sometimes "ARCHIVE" and sometimes "archive"! I completely deleted the whole sync partnership again, including deleting the CSC folder, and then re-synchronised my folders using only Windows XP on the server (which is the OS I still most use there) and I removed the shares on Windows 8.1 and Windows 98SE on the server. So far so good, the problem hasn't returned.

The XP Event Log links seem to have died again now. They all now seem to produce - "404 - File or directory not found." Have MS finally switched off the context sensitive online help for XP? I think they may well have died exactly a year after EOS, they've certainly not been working for a while now.

I just installed BlackWingCat's version of KB3037572 and KB3023211 (they're combined together in a single installer). No untoward effects so far (touch wood!) My internet security program flagged it as a suspicious file, as it did when I installed his other modified updater files in fact, and I had to switch it off temporarily, but no other issues.

I've installed all the offered updates for this month from Microsoft Update, and done the six .NET updates too. No problems so far, fingers crossed!

Hi again jaclaz! I had already followed the instructions on that link, in fact most of the references on the web to this sort of problem point to it! It didn't do any good unfortunately. The one puzzling thing was that adding the registry entry appeared to do absolutely nothing. It's supposed to re-initialise the cache, and then be deleted. In fact nothing happened at all when I re-booted after adding it, the cache remained exactly the same, and the registry entry was still there too! The article is for Windows XP of course, not Windows 8.1, although my research seemed to indicate that it should still work. I did find one suggestion to clear things by adding the FormatDatabase entry elsewhere, in HKLM\System\CurrentControlSet\Services\CSC\Parameters, instead of HKLM\Software\Microsoft\Windows\CurentVersion\NetCache. This just resulted in a rather frightening BSOD on startup saying KERNEL_SECURITY_CHECK_FAILURE, so I swiftly backed out of that! Just to give the exact setup, the server has a drive on it called "Archive" which I have shared, under that name, on Windows 8.1 and Windows XP. I used Offline Files on the client netbook to synchronise some folders on that drive, both on 8.1 and XP on the netbook. This worked fine for many months, until this error message started happening on synchronisation on the client, but only on 8.1, not on XP. Anyway, I've now tried some more tests. I have now removed sync for all folders and files except one single file on the archive drive, which is in the root of the drive. The error message is still appearing. I have now tried sharing another drive on the server, and again synchronising just one file in the root again as on the first drive. That drive syncs with no error message. So I now have two entries in the sync partnership, both syncing just one file, one of which works and the other doesn't! This indicates to me that the problem is actually on the server, with something about the Archive drive or its contents causing the problem, but I can't for the life of me see what it could be. The sharing of the two drives is set up identically. They are both FAT32 formatted drives. Any suggestions gratefully received!

So has no-one any experience of this at all? I should now mention that both the client and server machines have Windows XP installed on them as well as Windows 8.1, and offline files works perfectly on Windows XP on the client, and it doesn't matter whether the server is on Windows XP or Windows 8.1, in both cases Windows XP on the client works fine and Windows 8.1 throws the error. I am therefore assuming that the problem is on the client machine and not on the server. I've now tried de-synchronising all the synchronised folders on the client in Windows 8.1, leaving just one file synchronised on the client, which is in the root of the shared drive on the server. I'm still getting the "parameter is incorrect" message when I synchronise.

Which is why I said "All both those updates appeared to do...."! I'm well aware that all sorts of changes could have been made behind my back. Good or bad remains to be seen. I've now been on my main machine with Windows 8.1, and only KB3022345 was offered there. No reboot was required after the update as it was on the netbook, so I guess it was KB3048043 which needed that. No popups saying "Windows 10 is Ready" on the main machine as yet!

All both those updates appeared to do (well presumably one of them) was to add a shortcut to my start menu called "Windows 10 Technical Preview". Clicking on it just opens up the Windows Update page, and checking for updates shows nothing! Goodness know what all that was about!

LOL! Well, after I posted my last message, I fired up my Windows 8.1 netbook, and a popup appeared in the top right hand corner of the desktop saying "Windows 10 is Ready"! Surely not, I thought, and when I clicked on it Windows Update opened offering two optional updates, KB3022345, and KB3048043. The former is 383 KB, the latter 612 KB, so neither of them is going to be a new operating system! I'll install them and see what happens........... I thought Windows 10 wasn't supposed to be out until much later in the year.

I must say that I'm surprised to hear that Windows 10 is likely to be another free update. They offered the update from Windows 7 to Windows 8 at very low cost, and a free update from Windows 8 to Windows 8.1, but I assumed the latter was simply because Windows 8 was put out with so many things wrong with it, some of which 8.1 was an attempt to address. I never thought that the next "upgrade" would be free as well!

Does anyone here have experience with the Windows 8.1 Offline Files facility? I've been using it for quite a while to synchronise some folders on my main machine's archive drive with my netbook, and it's always worked very well until a few weeks ago. Now, although it still syncs OK, it's always showing an error after syncing. The error being thrown is that good old favourite "The parameter is Incorrect"! This is one of the most common and most annoying error messages there is IMO, as of course it gives you absolutely no clue as to what the "parameter" is that's incorrect, and in my experience there's almost always absolutely no way to find out! I have of course researched this, and the few bits of information I've found nearly all say to reset the store on the client side and basically start again. Well I did that, even going as far as you completely delete the CSC folder on the client machine, and re-did the whole sync partnership from scratch, which needless to say took hours! It worked fine for about a day and a half, and then the same error came back, with no apparent cause! As I said, it is actually syncing the files fine, and I have been monitoring the sync event log, and files are being transferred OK when they have changed or been added or removed on the server side or the client side. However, it still keeps throwing this wretched error so it always looks as if the sync has failed. The details view in the Event Log shows - - UserData - SyncFailureInfo Path \\ASHFIELDCOURT\Archive Operation Sync client copy to server ResultCode 0x80070057 Result The parameter is incorrect."ASHFIELDCOURT" is the name of my main computer, the server, and "Archive" is the name of the shared drive on that machine. Anyone any ideas, this is driving me nuts?! Cheers, Dave.

Another six optional updates this evening. All installed OK, a replacement KB3022345 did not seem to be among them!

Me too. I'm not at all worried about KB3022345, especially as it's now no longer being offered.

It looks like KB3022345 may have been pulled. Even though it didn't install, I'm no longer being offered it as an optional update. Presumably a fixed version is on its way!

It's been suggested here to manually download and install the update in your specific language. Unfortunately there is no download for different flavours of English, so that's no help to me as my system is UK English, on which it's failing, both from WU and from a manual install! I suppose I could try temporarily changing the system to US English, installing the patch, and then switching back again! What a PITA......

I installed eighteen .NET updates yesterday. No ill effects so far (touch wood!)

Goodness, I had no idea that there were so many! I only have the first two installed. Have they actually stopped offering .NET updates to POSReady machines through Windows Update? None of those were as far as I'm aware. I would have thought that there would be .NET applications running on machines with that flavour of OS.

Will those later .NET updates for Server 2003 install on XP as they are, or do they need to be modified? I only have KB2931352, KB2931365, and KB2932079 installed at the moment, and they were from modified installers.

Fair enough!