This happens regardless on Windows OS version:

AutoUpdate successfully recognizes a need for the new version on the server and starts the update process. The plugin is placed in the appropriate Extensions folder for the OS. Instead of moving the older plugin to the \Saved folder within the Extensions folder, it leaves it where it was and renames the new plugin 360Works_pluginname.fmx.new.

All other plugins from other vendors work as advertised.

Please help with this.

There was an issue with older versions of our plugins where files would not be released properly and auto-update would not work successfully. Our latest build of our plugins resolves this issue. You will need to either manually remove the old plugins from the auto-update directory before allowing the script to install the new versions, or you can use our plugin-remover utility on our site at http://360works.com/remove-plugins/ which will do this for you.