ok
Yes, your dump file tells so, and this should be ok, ...
but what is with other software about virtualizing and such?
DD.20151018.1510.CEST
No idea.
About what fact do you complain?
Is it the spelling error at "occured", instead of "occurred"?
Does the error situation happen all the time when you invoke Mp3tag?
Which type of files or folders or USB stick or whatever else is involved when invoking Mp3tag and which version and so on?
Say some words about the current environment, before Mp3tag creates the dump file.
DD.20151018.2015.CEST
I don't complain, I only want to use Mp3Tag.
The error message occurs everytime the program is started. Nothing special is involved, I click Mp3Tag (2.72) in the start menu of Windows.
I just found out I can use Mp3Tag until I select a choice in the error message then the program is closed.
Windows allows to start a program in a compatibility mode - have you tried one of these options?
(Honestly: if everything is OK in respect to hardware, OS, virtualization, access rights - then MP3tag should run without any glitches. So you have to help to look. E.g. there was a really strange error just because the system clock was completely out of sync. This is something you can never find out from the distance.)
In compatibility mode everything after XP sp3 is broken. XP sp3 and before or run as administrator solves the issue.
Are you satisfied with that solution?
i can only repeat: normally, MP3tag runs on W10 and 64 bits without any trouble. So it is a workaround that takes currently care of your special environment.
Until the next user reports something like this.
Yes it works fine now.
Fine? Are you sure?
Maybe there is a problem with uncorrect access rights, ...
regarding the rights for the Mp3tag's installation folder ....
and the rights for the user's %appdata% folder.
See also ...
/t/17116/1
DD.20151019.0117.CEST
I just got an idea: what about the access rights to respective registry sections, e.g. the shell extensions. So perhaps a check if these entries are up to date could give a hint.
Why would incorrect access rights only affect Mp3tag?
Hmm, maybe because Mp3tag does not share it's folders and scripts and other Mp3tag related objects to other applications or to several users at one time, ... therefore it is not of interest for other applications, whether there exist access problems in the domain of the Mp3tag application, ... I think so, but I do not know for sure, I am still on Win XP, and Mp3tag does what it can do.
I am on this theme here because of curiosity, into which complications can users run, when applying Mp3tag, in other ways than the author had thought of.
Maybe in a couple of hours you are able to tell us about the problem and where it was, ... within your computer or before or behind.
DD.20151019.1411.CEST
I think only the author could see why it needs to be run as administrator.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.