Tweaking.com Support Forums
Main Forum => Tweaking.com Support & Help => Topic started by: coover on February 06, 2016, 05:37:43 pm
-
When attempting to install 3.8.2 on Windows 10 Build 14257 (Preview Build), I get a "sharing violation while accessing C:\Programs Files (x86)\Tweaking.com\Windows Repair (All in One)\files\registry_backup_tool\TweakingImgCtl.ocx."
I realize that most folks do not have this build of Windows 10, but it is something you might want to take a look at, as I had the same issue with build 14251. With 14251, I was able to run the Portable version of Windows Repair, and I assume I could do so with this build, too.
-
I have the same problem.
-
Looks like a problem they will have to address. In the mean time, use the portable application.
-
Sharing violation means the setup or program tried to access the file but wasnt allowed. This is always caused by your antivirus. Disable the antivirus and install it again and you should be good :wink:
Shane
-
I use Windows Defender on the laptop now running version Build 14271, as I do on all my computers (4 Desktops and 5 laptops). The others use the standard version of Windows 10, Build 10586.104. I only have problems installing Tweaking.com Windows Repair on the laptop using build 14271. It seems strange that Windows Defender in the Build 14271 will interfere with the installation, while it will not interfere with the computers running Build 10586.
-
I should have mentioned above that I am now using version 3.8.3
-
Sharing violation means the setup or program tried to access the file but wasnt allowed. This is always caused by your antivirus. Disable the antivirus and install it again and you should be good :wink:
Shane
Confirmed. I did attempt to install version 3.8.3 with Windows Defender enabled and got the error message. I then disabled Windows Defender and 3.8.3 installed properly.
However, I can not mark this thread as solved until Windows Repair installs correctly with Windows Defender enabled, just as it does with Build 10560.
-
My program has nothing to do with how it installs and your antivirus combined. Your AV scans every file and it is your AV that is causing the problem, not windows and not my program.
Avs do this all the time, best you can do is send the file to them and they will remove any false positives from their virus defs.
Shane
-
Thanks, Shane. I know you guys are doing a wonderful job.