Windows 10 - COM surrogate issue
Musigny
Member Posts: 1,027
I don't know where to post this.
Since the November major update, Microsoft Windows 10 has many problems with its own "sandboxing" feature.
It has an impact on weidu. A Weidu executable is able to detect and upgrade other weidu executable programs found in the same directory (provided you have the right and/or ownership to do so) but now it cannot upgrade itself. You may have to run two different setup-somemod.exe files without installing anything in order to auto-upgrade all your weidu executables.
This is a widespread issue, not something specific to weidu. Apparently MS is not willing to fix this long standing issue. The underlying ideology is mimicking Android: you are too dumb to control your own system and to manage its security.
Since the November major update, Microsoft Windows 10 has many problems with its own "sandboxing" feature.
It has an impact on weidu. A Weidu executable is able to detect and upgrade other weidu executable programs found in the same directory (provided you have the right and/or ownership to do so) but now it cannot upgrade itself. You may have to run two different setup-somemod.exe files without installing anything in order to auto-upgrade all your weidu executables.
This is a widespread issue, not something specific to weidu. Apparently MS is not willing to fix this long standing issue. The underlying ideology is mimicking Android: you are too dumb to control your own system and to manage its security.
4
Comments
I've been using dual boot systems with Windows and Linux for over a decade, but it looks like my next one will have just Linux.
May be its the user account controls causing the problem.
According to Musigny it only bugs in that specific case.
COM surrogate has an issue that most people meet when they try to remove the meta info from a file.
Such has removing some data from a picture using the windows/explorer interface (properties/details/remove meta info and copy the file). The upgrade can not occur because the process is denied the right to overwrite the file (more exactly copy and paste a copy).
It happens on fresh a install of Win 10, it is not the result of a specific configuration by the user.
For sure you can install and play mods, my own BG(2)EE installations are on windows 10.
The typical case I am experiencing:
Unpack a couple of weidu mods, run one of them from the command line.
Failure to auto-update (other files would be updated):
Moreover a process (not the one you launched!) remains non terminated:
Actually perhaps not the COM surrogate itself but a function/services used in both cases.
And it does not seem to be a simple and basic ACL issue because a) it is clean afaik and b) all files have the same rights c) no resident antivirus or the like d) occurs on directory trees the acls of which have never been updated by the user.
I use a Unix-like system on a daily basis and I might have lost some experience on Windows (used for games and MS Visio or when I need flash) but there is clearly a problem here and I ahve been experiencing the issue since the November release.
I would be glad to know that people have no issue with Win10, that would help the problem determination.
The main difficulty is that I have no particular modification of the base install, except the parameters to shut up many apps which communicate with MS servers on the Internet. It was not sufficient (I have seen default install having more than one connection per minute to Microsoft) and I ended up filtering at the gateway firewall level but I digress.
We can take this to another thread or PM.
A public discussion about a new weidu distribution system is welcome, here or elsewhere.
Getting the weidu version of the binary is easy, "./weidu --version". That outputs a string to stdout in the format: Use a cURL command to api.github.com can get information on the latest release. This returns a string of the format: If the tag_name is set to a string like the WeiDU version number, e.g., "23800", it is should be easy to compare versions and see if a new download is needed.
http://www.theregister.co.uk/2016/02/02/microsoft_ups_pressure_win_10_holdouts
I'm a control freak, so guess which OS I personally prefer
If something has to be demonized (imho) is MS, not Win10, as going from 7 to 10 imo is not an upgrade of an OS, but an upgrade to a different OS. MS had offered in the recent past the OPTION to upgrade to 10, and that was fine and fair. To FORCE in that stealthy way the upgrade to people who had chosen to refuse it is no more fine and fair. An user of an OS is not supposed to have to defend himself from the OS developer, to be denied to the right of continuing to use what he had chosen and had payed for, to have to disable an useful functionality like the automatic updates.
Edited to add the imho
http://www.theverge.com/2016/2/2/10893620/microsoft-windows-10-upgrade-recommended-update