[BUG] Can't overwrite plugin file installer error

[damnedOperator]

Describe the bug
As mentioned in #31, I also get the error message from the installer that it couldn't overwrite the plugin file.

To Reproduce

1. Download latest release installer
2. Execute with administrator privileges
3. Keep "Install OBS-Plugin" checked in the installer
4. Proceed with the installer as usual

Expected behavior
The installer should finish as usual and OBS-Beam plugin should be available in my OBS instance.

Screenshots
Same error message as in #31

Logs and details about your system

No installer logs available.

• Windows 11 Pro 23H2
• OBS 30.1.2
• Beam 1.0.0
• Video Settings N/A (1920x1080, 50fps)
• 10G, 2.5G and 1G Networks attached

Additional context
The installation is contained in C:\Program Files\obs-studio so I am not running in portable mode.

[YorVeX]

Can you check please whether this file exists:
C:\Program Files\obs-studio\obs-plugins\64bit\xObsBeam.dll

And if it does, which version it has (just hover over it with the mouse cursor) and whether it has a file size greater than 0?

Also, please try to copy xObsBeam.dll to this location manually from the latest .7z file in the Releases section, does this work?

The things that come to my mind which could cause this would be:

• anti-virus software blocking it - temporarily disable it during Beam installation and see if the problem persists
• file already there from a previous installation and tried to install while OBS was running (on Windows, DLL files cannot be overwritten while they're being used)
• corrupted file system, e.g. due to a previous system crash, in this case running chkdsk on C: could help
• broken file permissions (it's possible to block write access even for admin processes, but could be fixed by manually resetting permissions from an admin account)

The first point would be a pretty common scenario, as OBS plugin installers in general often become victims of false positive detections by anti-virus software. That's because an OBS plugin installer is a self-extracting executable that writes to a protected system folder that is not even its own folder - unfortunately those are properties and behaviors very similar to that of actual viruses and trojans, hence they often trigger the heuristic detections of anti-virus software and there's not much I can do about it.