Have you tried these things:
http://www.techproceed.com/2014/05/how-to-delete-undeletable-or-locked-file.html
On Sun, 09 Aug 2015 16:46:37 +1200, Eric Stevens
<
eric.s...@sum.co.nz> wrote:
>I have a Dell XPS 8300 fitted with an i7. I am running Windows 7/64
>bit which as far as I know is fully updated. Certainly it is service
>pack 1. My major use of the machine is processing photographic images.
>
>For may years I have been keeping my screen profiles calibrated using
>the DataColor Spyder. I used the Spyder 4 Pro quite succesfully for a
>long time, until about mid June this year I found that every time I
>tried to save the profile after a new calibration I received the
>single-line message
>
> "SaveProfileUsingCM.DeleteFile failed
> [C:Windows\System32\Spool\drivers\color\<name>.icm"
>
>Where <name> is the chosen name of the profile.
>
>About a month ago I installed a Spyder 5 Pro, and I still have the
>same problem. I have been in touch with DataColor but so far they have
>not been able to come up with anything that helps.
>
>Today I have spent several hours experimenting with all kinds of
>possible variables but none of my trials have enabled me to save a
>profile. I always end up with the failure message. About all I have
>not done is invoke the command "net user administrator /active:yes"
>
>Changing the name of the profile has no effect. I have tried some
>ridiculous names and it is not likely that they all are under use by
>other software so a conflict or trying to delete a file that is
>already in use does not seem to be the explanation.
>
>I have disabled the relevant parts of my McAfee anti-virus software.
>
>I have explored file permissions and changed those of my original
>profile to include me as administrator.
>
>I have followed the Datacolor instructions for completely deleting all
>traces of Spyder, including removing all profiles associated with my
>monitors from the Windows color manager. I then reinstalled Spyder.
>
>I have installed and run Spyder 5 Pro immediately after creating an
>entirely new user with administrator privileges and virtually no
>startup software.
>
>None of these things have had any effect.
>
>I first encountered this problem in mid June whhen I was still using
>Spyder 4 Pro. The problem has continued with Spyder 5 Pro. This
>suggests that it arises from a body of code which is common to both
>Spyder 4 and Spyder 5. Unfortunately I don't know enough to suggest
>what it might be.
>
>I have used Spyder products for many years without any problems,
>including Spyder 4. It is likely that the problem arises from a change
>made by other software. I have all sorts of software which updates
>itself automatically and it is possible that the problem arises from
>one of these. The only software I have which might want to take over
>part of the color management is iTunes, Adobe CC and Windows.
>
>It is possible that iTunes may have updated in the month before the
>problem started, but I don't really know. I don't think it will be
>Adobe CC as, as far as I can remember, there had been no updates for
>some months until the arrival of CC 2015 about a week ago. Finally,
>there is Windows. Windows updates almost very Thursday and sometimes
>on days in between. If any outside software is likely to have
>triggered this problem, Windows would be my chief suspect.
>
>Finally, there is the Microsoft Community post at
>
http://tinyurl.com/nsrqlaa. This suggests that I am not alone with
>this problem. I was interested to note that the writer was using a
>Dell XPS laptop. I am using a Dell XPS 8300 desk top. Is this a
>coincidence? I've had no changes or updates as far as I know.