Also, the following readings might be of some interest:

http://forums.cnet.com/7723-6122_102-57 ... n-restart/

http://answers.microsoft.com/en-us/wind ... 2a69c88533

There are some relativly new nasties roaming that revert changes to prevent the user from getting rid of it.

EDIT: And check my previous message on the other page.

Done, instructions followed to the letter, 4 files emailed.

Ok, let me ask you a question: after the reboot, did your dock revert back to default?

Because from what I see in the four registry files, they are ALL the same, all your dock icons and settings are there *at all times*.

Yes, it did revert back.

Getting stranger and stranger, eh?

Upgraded to 16.2, but had to do it manually on the problem PC, the others asked!!

Issue still there. I did get, on all PC's, a box to allow from Webroot. I don't remember getting that before. Two actually, probably for Menu and Shelf. I also set up an ALLOW for the EXE's in Webroot, but that hasn't fixed it either, it seems.

I ended up not having the chance to get to the bottom of this before the release deadline, sorry. I did try.

And I did read your suggested sites above and tried some stuff, malware scans, of which I run Malwarebytes Pro actively anyway, and sfc /scannow, which found one thing but nothing that fixed my problem.

I guess I'll just live with it and restore on reboot!! Not that big a deal, but certainly curious seeing as I run this on 4 pc's that are all on 24/7. One thing, this one pc with the issue is Windows 10 Pro where the others are Windows 10 Home. Wonder if there's something there?

I doubt it. It could be a Group Policy, if it weren't for the fact that the Registry Settings are NOT actually reset after a reboot. They're still there, it's just like they are not being read (or there is some kind of an error when they are being read) and the dock resorts to using the defaults.

Hmmm, don't remember if I already asked this question or not: what happens if you restart WorkShelf without rebooting your machine?

Stopping and restarting workshelf does the same as rebooting. You had me run thru a bunch of steps originally and send you backup files, 4 of 'em, and you said they were identical, where, apparently, they shouldn't be identical given the circumstances (adding a dock item and saving, etc.)

Ok, this is one important piece of information. I smell a reading error of some kind. OR an access problem.

Just wanted to add a comment to that. My initial purpose what to determine if the settings were being reset at a Registry level, and, if so, when. With your help I accomplished this goal, we now know that the settings themselves are there, they're simply not being read back into memory for some reason yet unknown.

As far as the temporary changes you made not being saved, this could be because Nexus/WorkShelf uses a sort of 'write cache' for performance reasons. In order to prevent the application from stuttering (because it's writing a ton of data to disk) every time you add, edit or remove items from docks and the shelf, the changes are only committed to memory initially.

These changes will only be saved to disk when you exit the application _OR_ as soon as the system has been idle for a couple of minutes. The latter minimizes the chance of a system crash wiping out your changes.

We can consider this done. The motherboard on that computer took a dump so it's over!! I built a new computer, installed Winstep Extreme, it works fine.

You know, that pc was the ONLY one I had that was UPGRADED from Windows 7 to Windows 10 and never reinstalled clean after getting a license. I seldom do that, upgrade to a newer OS, normally taking the time to do a clean install and reinstall everything. One more step there now with the "Free" Windows 10 thing, you have to "upgrade" to get a license, than reinstall clean to get a clean install, and I got lazy on that one!!

Oh, well, one thing learned thru this is that Winstep support is great!!

Thanks again,
Tom

Glad it worked out great for you in the end!

I hate it when 'bugs' like this happen, because without access to the physical machine I cannot even begin to understand what is happening (the first step in fixing any problem).

But, as you can see, sometimes a bug is not really a bug, just some weird interaction between hardware or software or God knows what else - on that specific machine only. Normally the user only fully realizes this when he installs the same software on a different machine and the problem 'magically' goes away.