Patching error

[Adv]

Thoughts?

 

[Babyhack]

Run as admin and download the new patch program?

BH

 

[Samuel]

Thoughts?

Says access to your mir2.exe is denied... Strange...

Is the mir2.exe actually in "C:\Users\Dave\Desktop\Chronicles\"? If not, what virus checking software do you use?

Sam

 

[Adv]

Always run as admin.

AV is disabled when patching.

Cant work it out either. Laptop literally hasnt been turned on in 6 weeks, nothing has changed since i last played.

 

[Babyhack]

Always run as admin.

AV is disabled when patching.

Cant work it out either. Laptop literally hasnt been turned on in 6 weeks, nothing has changed since i last played.

A new version of the patch program was released a couple of days ago

BH

 

[Samuel]

Always run as admin.

AV is disabled when patching.

Cant work it out either. Laptop literally hasnt been turned on in 6 weeks, nothing has changed since i last played.

The mir2.exe is in the folder?

Sam

 

[Adv]

I have the latest patcher files.

.exe is in folder yes, but says i dont have permission to execute it.

---------- Post Merged at 01:28 PM ---------- Previous Post was at 01:09 PM ----------

Cracked it, was an old version of AVG still active blocking downloads.

Spoke too soon, managed to download 17 of 18 files, exception being the exe. Getting unhandled error.

All AV and firewalls disabled and running as admin. Perplexed lol.

 

[Samuel]

All fixed... Another case of AVG being a dick as of recently...

Note for me and BH, we must find out why AVG suddenly hates us.

Sam

 

[Adv]

Pfft. popped for a drink and it was done! Explain!

 

[Samuel]

Pfft. popped for a drink and it was done! Explain!

Lol,

AVG was still running some services in background... I opened up AVG, made sure the shield was disabled (advanced settings > computer protection > anti virus), which it was, so I disabled the lot (temporarily disable AVG protection), it will come back to life next time you reboot though.

We are not sure what has happened, either AVG have had an update and this likes something about the mir2.exe (potentially what we pack it with) OR, they have pulled in a list of reported threats and someone has reported "mir2.exe" in the past... Both are likely.

Sam