Have nlog file permissions changed in the latest windows 10 update?

Question

0.00/5 (No votes)

See more:

I have been using NLog in a WPF application for some months. I am developing in Visual Studio 2015 on Windows 10.

I write from my application using NLog into \bin\Debug\Logs. Suddenly I find I do not have permission to delete log files in this directory. And this obviously propagates up the directory tree, so I cannot delete the \bin folder in Explorer.

I do run Visual Studio as Administrator. I switched to doing this to fix a problem I had ages ago (can't remember what the specific issue was), but it has never stopped me deleting NLog files before now.

I did get a Windows Update a few days ago. Does anyone know if there has been a change that might be causing this behaviour?

I would also appreciate any suggestions about how to fix this.

What I have tried:

Even attempting to do this in a command prompt with Administrator permission fails with 'Access is denied'.

I cannot take ownership of the file either. If I try to do this in Explorer, I get a message saying, 'You must have Read permissions to view the properties of this object.'

Posted 13-Jun-17 23:22pm

Patrick Skelton

Updated 13-Jun-17 23:34pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Patrick Skelton · Accepted Answer · 2017-06-13T23:34:00

This turned out to be the Gamut File Viewer (www.gamutsoftware.com), which I have just started using (that should have been my clue). Reading the docs, it seems it has the functionality to clear the log file, which probably means it keeps a permanent lock on the file.

I am surprised that I was even denied Read permission though.

I was going to delete this question, but then I thought it might have value to anyone else who chooses to use this fairly common set of tools.