Search code examples
windows-vistafilesystemsshadow-copy

Strange, possible “shadow copy” issue where two editors show different contents

I have some code that is reading a config file, but when I open the file in TextPad, I see different values than my application does. I checked it with Notepad. Notepad agrees with my application, TextPad shows something else.

This is on Vista x64 Business.

Any idea what could be causing this? I've looked in the Context Menu->Properties->Previous Versions details, but it says "There are no previous versions available".

Here's the steps to replicate (I can't make it happen reliably):

  1. Installed .NET app in Program files.
  2. That app reads the config file, but is falling over.
  3. I manually edit that config file in Textpad.
  4. The change doesn't take effect.
  5. I open the config file in Notepad, and see something different.
  6. Try making the change in Notepad and saving, and get this error message:

Notepad

Cannot create the C:\Program Files (x86)\Daniel Schaffer\WorkingOn for FogBugz\FogBugz > WorkingOn.exe.config file.

Make sure that the path and file name are correct.

I can't put the content here as it's XML and is being encoded by Superuser.com, but here's a link to a screencast: http://screencast.com/t/zhERl7mocp4.

Solution

  • Sounds like a case of you don't have administrator privs, when you installed your app. Sometimes when you install an app with no admin privs, it behave really strangely because of vista security model. I had a similar problem to this last year. It wasn't the exactly, but it was strange behaviour, until I figured out it was vista's security model. It elevates it into application/user security context, from what I know, as my brain froze when I was reading about it, as it was pure muck and virtually useless from what I can see.

    Try opening Textpad (excellent app) with Run as Administrator, and then edit the config. See what happens. If it stays then same then its a prives problem. If that doesn't work, deinstall you app, and then install it as an administrator. That will give the app the write admin privs to work. Then when you edit the config. See if that works.

    Take a look at this. You can elevate an app to run as administrator, Using the techniques found here. How to elevate an application.. Try all these before you do a reinstall.

    If that doesn't work, post your question to server fault. Also post it to a suitable MSDN forum.

    Hope that help. Bob.