Windows 10: Windows Defender and .ini files

We ae using Windows 10 and Windows Defender antivirus.

When our program saves information to an .ini file - it can take a very long time. It takes more than 4 times longer with Windows Defender than with other anti-virus programs ex AVG, Avast. If we exclude the .ini file from Windows Defender - it also is OK. BUT if this .ini file is included in the antivirus to be checked a certain part of this file We have narrowed down the section can take 4 times longer to save to the .ini with Windows Defender only.


What could be the cause of this? What kind of .ini action would cause this? No other antivirus causes this to happen.


Any suggestions - other than excluding this file from Windows Defender?


Shimon

:)

 

Snippet C#: INI Files

This code is great, i'm going to use this in one of my programmes *Big Grin

is it possible to make a list of all sections in the ini files?

 

Snippet C#: INI Files

GetSections() will return a string[] of section names. If you want the values too, just do a for or for loop to enumerate them. For example:

Code: foreach (string section in ini.GetSections()) { Console.WriteLine("[" + section + "]"); foreach (string key in ini[section].GetKeys()) Console.WriteLine(key + "=" + ini[section][key]); Console.WriteLine(); }[/quote]

 

Windows 7 Cannot Read .ini File

I am working on a Windows 7 Pro computer and trying to connect a signature pad (SigPlus), and the device is not USB compatible. So during install, I had to select the COM1 option, but the issue is that the desktop only has a COM6 port. I have a .ini (configuration
setup) file that is supposed to change the port configuration, but Windows refuses to read the file. I have followed the SigPlus instructions and put the .ini file in the Windows folder. I noticed it was still not working so I put the .ini file on the server,
thinking that the system required them to match, but that did not work either. Someone suggested I should do compatibility mode, but I am not sure that would solve the issue. Also, another issue is that I have administrative credentials but the system I am
working on does not. I have been putting the .ini file on a shared company drive to transfer to the correct folders.