Error: MikTex console already running The Next CEO of Stack OverflowMikTex Console already runningWhy Windows API 5 error when running initexmf in MiKTeX?LyX & MiKTeX installation problems on Windows 7Missing .dll file prevents MiKTeX package manager from openingMikTeX Update corrupts the installationMikTeX 2.9 does not respond under Windows 10 Pro 64 bitError with BibTeX when compiling in MiKTeXProblem installing MikTex 2.9 on Windows 10 (64 bit)Unable to uninstall MikTeX from Windows 10MikTex Console already runningMikTeX Console stop working
Multi tool use
Why do professional authors make "consistency" mistakes? And how to avoid them?
How to write the block matrix in LaTex?
How can I get the renderings when using the Find-Item command?
At which OSI layer a user-generated data resides?
Help understanding this unsettling image of Titan, Epimetheus, and Saturn's rings?
Why did we only see the N-1 starfighters in one film?
Horror movie/show or scene where a horse creature opens its mouth really wide and devours a man in a stables
Was a professor correct to chastise me for writing "Prof. X" rather than "Professor X"?
How do scammers retract money, while you can’t?
LWC - Unit Testing NavigationMixin.GenerateUrl
Path-continuity and the Axiom of Choice
What is the purpose of the Evocation wizard's Potent Cantrip feature?
India just shot down a satellite from the ground. At what altitude range is the resulting debris field?
Is it safe to use c_str() on a temporary string?
How can I quit an app using Terminal?
Return the Closest Prime Number
What's the Pac-Man-like video game seen in the movie "Joysticks"?
WOW air has ceased operation, can I get my tickets refunded?
Can a caster that cast Polymorph on themselves stop concentrating at any point even if their Int is low?
Why do remote companies require working in the US?
How to get regions to plot as graphics
How do we know the LHC results are robust?
How to make a variable always equal to the result of some calculations?
How can I get through very long and very dry, but also very useful technical documents when learning a new tool?
Error: MikTex console already running
The Next CEO of Stack OverflowMikTex Console already runningWhy Windows API 5 error when running initexmf in MiKTeX?LyX & MiKTeX installation problems on Windows 7Missing .dll file prevents MiKTeX package manager from openingMikTeX Update corrupts the installationMikTeX 2.9 does not respond under Windows 10 Pro 64 bitError with BibTeX when compiling in MiKTeXProblem installing MikTex 2.9 on Windows 10 (64 bit)Unable to uninstall MikTeX from Windows 10MikTex Console already runningMikTeX Console stop working
When I try opening the MikTex console I get an error window saying "MiKTeX Console is already running". I tried closing literally every program, and I still get it. I opened Task Manager to see if it showed up there, but no. I tried restarting my laptop. I tried running the console as an administrator, but I get the same message. Any help? Thank you.
miktex
asked Feb 2 at 13:49
romuloromulo
1
add a comment |
When I try opening the MikTex console I get an error window saying "MiKTeX Console is already running". I tried closing literally every program, and I still get it. I opened Task Manager to see if it showed up there, but no. I tried restarting my laptop. I tried running the console as an administrator, but I get the same message. Any help? Thank you.
miktex
asked Feb 2 at 13:49
romuloromulo
1
1
Maybe tex.stackexchange.com/questions/443378/… gives some hints.
– albert
Feb 2 at 14:33
add a comment |
When I try opening the MikTex console I get an error window saying "MiKTeX Console is already running". I tried closing literally every program, and I still get it. I opened Task Manager to see if it showed up there, but no. I tried restarting my laptop. I tried running the console as an administrator, but I get the same message. Any help? Thank you.
miktex
asked Feb 2 at 13:49
romuloromulo
1
When I try opening the MikTex console I get an error window saying "MiKTeX Console is already running". I tried closing literally every program, and I still get it. I opened Task Manager to see if it showed up there, but no. I tried restarting my laptop. I tried running the console as an administrator, but I get the same message. Any help? Thank you.
miktex
miktex
asked Feb 2 at 13:49
romuloromulo
1
asked Feb 2 at 13:49
romuloromulo
1
asked Feb 2 at 13:49
romuloromulo
1
asked Feb 2 at 13:49
romuloromulo
1
asked Feb 2 at 13:49
romuloromulo
1
1
1
Maybe tex.stackexchange.com/questions/443378/… gives some hints.
– albert
Feb 2 at 14:33
add a comment |
1
Maybe tex.stackexchange.com/questions/443378/… gives some hints.
– albert
Feb 2 at 14:33
1
1
Maybe tex.stackexchange.com/questions/443378/… gives some hints.
– albert
Feb 2 at 14:33
Maybe tex.stackexchange.com/questions/443378/… gives some hints.
– albert
Feb 2 at 14:33
add a comment |
3 Answers
3
active
oldest
votes
When launching MiKTeX-console via a .bat / .cmd file or shortcut it will usually show as an icon, however if you don't have show all icons it may not be visible.
You may need to expand all icons to locate it in the taskbar then you should be able to right click and control it. That is preferable rather than using > to expand the Windows Command Processor and killing it there.
It is possible in a dual set-up of Administrator & User that is is running under the other login. to avoid any update problems ensure the user session is not activated by your editor.
To trouble-shoot a dual install log in as user first, check NO editor or Console is active. Log-off as user and login as administrator, DO NOT run any LaTeX related application prior to running MiKTeX-console and if you see this message again you will need to re-boot to flush all active threads.
You should review your launch methods to avoid any dual loading in the first place, and without going into any detail here, there are ways to auto detect and killtask prior to relaunch but that is outside the scope of this site, it should not be necessary and best asked on other stack exchange forums.
answered Feb 2 at 17:06
KJOKJO
3,5101222
add a comment |
When I was in this situation, I found that MiKTeX had generated a file named miktex-console.lock in my user folder (C:UsersMyUsername for Windows users). Deleting the file permitted the application to run.
It appears that the MiKTeX console, for whatever ridiculous reason, does not simply check for other instances of the miktex-console.exe process, and instead generates this "miktex-console.lock" file when launched. Deleting the offending file whenever it is created lets you run as many MiKTeX console instances as you like.
This is horrifically bad design.
answered 14 hours ago
TiberiumFusionTiberiumFusion
112
New contributor
TiberiumFusion is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
It may be possible that in your case the lock file is stopping another MiKTeX session However that is not a reason for the error message as shown in this question. In most cases when MiKTeX crashes or otherwise leaves the lock behind it will normally just reuse it the next time then delete on clean closure. The problem here is that either the file is locked by another application or a second session held open most often by a pdf reader a virus checker or an editor not letting go, hence the need to shut down all memory. Your view is most valid perhaps if MiKTeX cant reset a read only lock file.
– KJO
13 hours ago
@KJO Yet, the symptoms shown by the OP are the exact conditions I experienced (no running MiKTeX processes of any kind, but attempting to start the console yields the "already running" prompt). While I don't know the application's requirements, the "already running" message implies an intent to prevent multiple instances of the console from running. Leveraging the filesystem exclusively for this task, thus introducing all the opportunities for issue that you mentioned (and more), is needlessly roundabout and very bad practice.
– TiberiumFusion
9 hours ago
I agree that your experience is totally valid and gave +1 for the alternative reason I had forgotten. However in testing I found that the presence of an old lock file did not make a fresh starting MiKTeX complain of one active it simply replaced the lock file. I am single user with elevated privilege so may have greater sway than basic user to cause such behaviour. As you may note another answer where user elevated themselves to admin at system level & say that was their solution. My view is that dual users may have basic user &admin user conflicts & the simplest way to untangle is to log off
– KJO
8 hours ago
add a comment |
Well, go on MikTex Console icon, clic onto it with the right button, then click on Other and then click on Execute as Administrator. it should open (at least it opens to me). But don't you think your problems are over with MikTex...
answered Feb 5 at 17:31
AndreaAndrea
1
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f473031%2ferror-miktex-console-already-running%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
When launching MiKTeX-console via a .bat / .cmd file or shortcut it will usually show as an icon, however if you don't have show all icons it may not be visible.
You may need to expand all icons to locate it in the taskbar then you should be able to right click and control it. That is preferable rather than using > to expand the Windows Command Processor and killing it there.
It is possible in a dual set-up of Administrator & User that is is running under the other login. to avoid any update problems ensure the user session is not activated by your editor.
To trouble-shoot a dual install log in as user first, check NO editor or Console is active. Log-off as user and login as administrator, DO NOT run any LaTeX related application prior to running MiKTeX-console and if you see this message again you will need to re-boot to flush all active threads.
You should review your launch methods to avoid any dual loading in the first place, and without going into any detail here, there are ways to auto detect and killtask prior to relaunch but that is outside the scope of this site, it should not be necessary and best asked on other stack exchange forums.
answered Feb 2 at 17:06
KJOKJO
3,5101222
add a comment |
When launching MiKTeX-console via a .bat / .cmd file or shortcut it will usually show as an icon, however if you don't have show all icons it may not be visible.
You may need to expand all icons to locate it in the taskbar then you should be able to right click and control it. That is preferable rather than using > to expand the Windows Command Processor and killing it there.
It is possible in a dual set-up of Administrator & User that is is running under the other login. to avoid any update problems ensure the user session is not activated by your editor.
To trouble-shoot a dual install log in as user first, check NO editor or Console is active. Log-off as user and login as administrator, DO NOT run any LaTeX related application prior to running MiKTeX-console and if you see this message again you will need to re-boot to flush all active threads.
You should review your launch methods to avoid any dual loading in the first place, and without going into any detail here, there are ways to auto detect and killtask prior to relaunch but that is outside the scope of this site, it should not be necessary and best asked on other stack exchange forums.
answered Feb 2 at 17:06
KJOKJO
3,5101222
add a comment |
When launching MiKTeX-console via a .bat / .cmd file or shortcut it will usually show as an icon, however if you don't have show all icons it may not be visible.
You may need to expand all icons to locate it in the taskbar then you should be able to right click and control it. That is preferable rather than using > to expand the Windows Command Processor and killing it there.
It is possible in a dual set-up of Administrator & User that is is running under the other login. to avoid any update problems ensure the user session is not activated by your editor.
To trouble-shoot a dual install log in as user first, check NO editor or Console is active. Log-off as user and login as administrator, DO NOT run any LaTeX related application prior to running MiKTeX-console and if you see this message again you will need to re-boot to flush all active threads.
You should review your launch methods to avoid any dual loading in the first place, and without going into any detail here, there are ways to auto detect and killtask prior to relaunch but that is outside the scope of this site, it should not be necessary and best asked on other stack exchange forums.
answered Feb 2 at 17:06
KJOKJO
3,5101222
When launching MiKTeX-console via a .bat / .cmd file or shortcut it will usually show as an icon, however if you don't have show all icons it may not be visible.
You may need to expand all icons to locate it in the taskbar then you should be able to right click and control it. That is preferable rather than using > to expand the Windows Command Processor and killing it there.
It is possible in a dual set-up of Administrator & User that is is running under the other login. to avoid any update problems ensure the user session is not activated by your editor.
To trouble-shoot a dual install log in as user first, check NO editor or Console is active. Log-off as user and login as administrator, DO NOT run any LaTeX related application prior to running MiKTeX-console and if you see this message again you will need to re-boot to flush all active threads.
You should review your launch methods to avoid any dual loading in the first place, and without going into any detail here, there are ways to auto detect and killtask prior to relaunch but that is outside the scope of this site, it should not be necessary and best asked on other stack exchange forums.
answered Feb 2 at 17:06
KJOKJO
3,5101222
edited Feb 5 at 17:54
answered Feb 2 at 17:06
KJOKJO
3,5101222
answered Feb 2 at 17:06
KJOKJO
3,5101222
answered Feb 2 at 17:06
KJOKJO
3,5101222
3,5101222
add a comment |
add a comment |
When I was in this situation, I found that MiKTeX had generated a file named miktex-console.lock in my user folder (C:UsersMyUsername for Windows users). Deleting the file permitted the application to run.
It appears that the MiKTeX console, for whatever ridiculous reason, does not simply check for other instances of the miktex-console.exe process, and instead generates this "miktex-console.lock" file when launched. Deleting the offending file whenever it is created lets you run as many MiKTeX console instances as you like.
This is horrifically bad design.
answered 14 hours ago
TiberiumFusionTiberiumFusion
112
New contributor
TiberiumFusion is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
It may be possible that in your case the lock file is stopping another MiKTeX session However that is not a reason for the error message as shown in this question. In most cases when MiKTeX crashes or otherwise leaves the lock behind it will normally just reuse it the next time then delete on clean closure. The problem here is that either the file is locked by another application or a second session held open most often by a pdf reader a virus checker or an editor not letting go, hence the need to shut down all memory. Your view is most valid perhaps if MiKTeX cant reset a read only lock file.
– KJO
13 hours ago
@KJO Yet, the symptoms shown by the OP are the exact conditions I experienced (no running MiKTeX processes of any kind, but attempting to start the console yields the "already running" prompt). While I don't know the application's requirements, the "already running" message implies an intent to prevent multiple instances of the console from running. Leveraging the filesystem exclusively for this task, thus introducing all the opportunities for issue that you mentioned (and more), is needlessly roundabout and very bad practice.
– TiberiumFusion
9 hours ago
I agree that your experience is totally valid and gave +1 for the alternative reason I had forgotten. However in testing I found that the presence of an old lock file did not make a fresh starting MiKTeX complain of one active it simply replaced the lock file. I am single user with elevated privilege so may have greater sway than basic user to cause such behaviour. As you may note another answer where user elevated themselves to admin at system level & say that was their solution. My view is that dual users may have basic user &admin user conflicts & the simplest way to untangle is to log off
– KJO
8 hours ago
add a comment |
When I was in this situation, I found that MiKTeX had generated a file named miktex-console.lock in my user folder (C:UsersMyUsername for Windows users). Deleting the file permitted the application to run.
It appears that the MiKTeX console, for whatever ridiculous reason, does not simply check for other instances of the miktex-console.exe process, and instead generates this "miktex-console.lock" file when launched. Deleting the offending file whenever it is created lets you run as many MiKTeX console instances as you like.
This is horrifically bad design.
answered 14 hours ago
TiberiumFusionTiberiumFusion
112
New contributor
TiberiumFusion is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
It may be possible that in your case the lock file is stopping another MiKTeX session However that is not a reason for the error message as shown in this question. In most cases when MiKTeX crashes or otherwise leaves the lock behind it will normally just reuse it the next time then delete on clean closure. The problem here is that either the file is locked by another application or a second session held open most often by a pdf reader a virus checker or an editor not letting go, hence the need to shut down all memory. Your view is most valid perhaps if MiKTeX cant reset a read only lock file.
– KJO
13 hours ago
@KJO Yet, the symptoms shown by the OP are the exact conditions I experienced (no running MiKTeX processes of any kind, but attempting to start the console yields the "already running" prompt). While I don't know the application's requirements, the "already running" message implies an intent to prevent multiple instances of the console from running. Leveraging the filesystem exclusively for this task, thus introducing all the opportunities for issue that you mentioned (and more), is needlessly roundabout and very bad practice.
– TiberiumFusion
9 hours ago
I agree that your experience is totally valid and gave +1 for the alternative reason I had forgotten. However in testing I found that the presence of an old lock file did not make a fresh starting MiKTeX complain of one active it simply replaced the lock file. I am single user with elevated privilege so may have greater sway than basic user to cause such behaviour. As you may note another answer where user elevated themselves to admin at system level & say that was their solution. My view is that dual users may have basic user &admin user conflicts & the simplest way to untangle is to log off
– KJO
8 hours ago
add a comment |
When I was in this situation, I found that MiKTeX had generated a file named miktex-console.lock in my user folder (C:UsersMyUsername for Windows users). Deleting the file permitted the application to run.
It appears that the MiKTeX console, for whatever ridiculous reason, does not simply check for other instances of the miktex-console.exe process, and instead generates this "miktex-console.lock" file when launched. Deleting the offending file whenever it is created lets you run as many MiKTeX console instances as you like.
This is horrifically bad design.
answered 14 hours ago
TiberiumFusionTiberiumFusion
112
New contributor
TiberiumFusion is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
When I was in this situation, I found that MiKTeX had generated a file named miktex-console.lock in my user folder (C:UsersMyUsername for Windows users). Deleting the file permitted the application to run.
It appears that the MiKTeX console, for whatever ridiculous reason, does not simply check for other instances of the miktex-console.exe process, and instead generates this "miktex-console.lock" file when launched. Deleting the offending file whenever it is created lets you run as many MiKTeX console instances as you like.
This is horrifically bad design.
answered 14 hours ago
TiberiumFusionTiberiumFusion
112
New contributor
TiberiumFusion is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 14 hours ago
TiberiumFusionTiberiumFusion
112
New contributor
TiberiumFusion is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 14 hours ago
TiberiumFusionTiberiumFusion
112
answered 14 hours ago
TiberiumFusionTiberiumFusion
112
112
New contributor
TiberiumFusion is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
TiberiumFusion is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
TiberiumFusion is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
It may be possible that in your case the lock file is stopping another MiKTeX session However that is not a reason for the error message as shown in this question. In most cases when MiKTeX crashes or otherwise leaves the lock behind it will normally just reuse it the next time then delete on clean closure. The problem here is that either the file is locked by another application or a second session held open most often by a pdf reader a virus checker or an editor not letting go, hence the need to shut down all memory. Your view is most valid perhaps if MiKTeX cant reset a read only lock file.
– KJO
13 hours ago
@KJO Yet, the symptoms shown by the OP are the exact conditions I experienced (no running MiKTeX processes of any kind, but attempting to start the console yields the "already running" prompt). While I don't know the application's requirements, the "already running" message implies an intent to prevent multiple instances of the console from running. Leveraging the filesystem exclusively for this task, thus introducing all the opportunities for issue that you mentioned (and more), is needlessly roundabout and very bad practice.
– TiberiumFusion
9 hours ago
I agree that your experience is totally valid and gave +1 for the alternative reason I had forgotten. However in testing I found that the presence of an old lock file did not make a fresh starting MiKTeX complain of one active it simply replaced the lock file. I am single user with elevated privilege so may have greater sway than basic user to cause such behaviour. As you may note another answer where user elevated themselves to admin at system level & say that was their solution. My view is that dual users may have basic user &admin user conflicts & the simplest way to untangle is to log off
– KJO
8 hours ago
add a comment |
1
It may be possible that in your case the lock file is stopping another MiKTeX session However that is not a reason for the error message as shown in this question. In most cases when MiKTeX crashes or otherwise leaves the lock behind it will normally just reuse it the next time then delete on clean closure. The problem here is that either the file is locked by another application or a second session held open most often by a pdf reader a virus checker or an editor not letting go, hence the need to shut down all memory. Your view is most valid perhaps if MiKTeX cant reset a read only lock file.
– KJO
13 hours ago
@KJO Yet, the symptoms shown by the OP are the exact conditions I experienced (no running MiKTeX processes of any kind, but attempting to start the console yields the "already running" prompt). While I don't know the application's requirements, the "already running" message implies an intent to prevent multiple instances of the console from running. Leveraging the filesystem exclusively for this task, thus introducing all the opportunities for issue that you mentioned (and more), is needlessly roundabout and very bad practice.
– TiberiumFusion
9 hours ago
I agree that your experience is totally valid and gave +1 for the alternative reason I had forgotten. However in testing I found that the presence of an old lock file did not make a fresh starting MiKTeX complain of one active it simply replaced the lock file. I am single user with elevated privilege so may have greater sway than basic user to cause such behaviour. As you may note another answer where user elevated themselves to admin at system level & say that was their solution. My view is that dual users may have basic user &admin user conflicts & the simplest way to untangle is to log off
– KJO
8 hours ago
1
1
It may be possible that in your case the lock file is stopping another MiKTeX session However that is not a reason for the error message as shown in this question. In most cases when MiKTeX crashes or otherwise leaves the lock behind it will normally just reuse it the next time then delete on clean closure. The problem here is that either the file is locked by another application or a second session held open most often by a pdf reader a virus checker or an editor not letting go, hence the need to shut down all memory. Your view is most valid perhaps if MiKTeX cant reset a read only lock file.
– KJO
13 hours ago
It may be possible that in your case the lock file is stopping another MiKTeX session However that is not a reason for the error message as shown in this question. In most cases when MiKTeX crashes or otherwise leaves the lock behind it will normally just reuse it the next time then delete on clean closure. The problem here is that either the file is locked by another application or a second session held open most often by a pdf reader a virus checker or an editor not letting go, hence the need to shut down all memory. Your view is most valid perhaps if MiKTeX cant reset a read only lock file.
– KJO
13 hours ago
@KJO Yet, the symptoms shown by the OP are the exact conditions I experienced (no running MiKTeX processes of any kind, but attempting to start the console yields the "already running" prompt). While I don't know the application's requirements, the "already running" message implies an intent to prevent multiple instances of the console from running. Leveraging the filesystem exclusively for this task, thus introducing all the opportunities for issue that you mentioned (and more), is needlessly roundabout and very bad practice.
– TiberiumFusion
9 hours ago
@KJO Yet, the symptoms shown by the OP are the exact conditions I experienced (no running MiKTeX processes of any kind, but attempting to start the console yields the "already running" prompt). While I don't know the application's requirements, the "already running" message implies an intent to prevent multiple instances of the console from running. Leveraging the filesystem exclusively for this task, thus introducing all the opportunities for issue that you mentioned (and more), is needlessly roundabout and very bad practice.
– TiberiumFusion
9 hours ago
I agree that your experience is totally valid and gave +1 for the alternative reason I had forgotten. However in testing I found that the presence of an old lock file did not make a fresh starting MiKTeX complain of one active it simply replaced the lock file. I am single user with elevated privilege so may have greater sway than basic user to cause such behaviour. As you may note another answer where user elevated themselves to admin at system level & say that was their solution. My view is that dual users may have basic user &admin user conflicts & the simplest way to untangle is to log off
– KJO
8 hours ago
I agree that your experience is totally valid and gave +1 for the alternative reason I had forgotten. However in testing I found that the presence of an old lock file did not make a fresh starting MiKTeX complain of one active it simply replaced the lock file. I am single user with elevated privilege so may have greater sway than basic user to cause such behaviour. As you may note another answer where user elevated themselves to admin at system level & say that was their solution. My view is that dual users may have basic user &admin user conflicts & the simplest way to untangle is to log off
– KJO
8 hours ago
add a comment |
Well, go on MikTex Console icon, clic onto it with the right button, then click on Other and then click on Execute as Administrator. it should open (at least it opens to me). But don't you think your problems are over with MikTex...
answered Feb 5 at 17:31
AndreaAndrea
1
add a comment |
Well, go on MikTex Console icon, clic onto it with the right button, then click on Other and then click on Execute as Administrator. it should open (at least it opens to me). But don't you think your problems are over with MikTex...
answered Feb 5 at 17:31
AndreaAndrea
1
add a comment |
Well, go on MikTex Console icon, clic onto it with the right button, then click on Other and then click on Execute as Administrator. it should open (at least it opens to me). But don't you think your problems are over with MikTex...
answered Feb 5 at 17:31
AndreaAndrea
1
Well, go on MikTex Console icon, clic onto it with the right button, then click on Other and then click on Execute as Administrator. it should open (at least it opens to me). But don't you think your problems are over with MikTex...
answered Feb 5 at 17:31
AndreaAndrea
1
answered Feb 5 at 17:31
AndreaAndrea
1
answered Feb 5 at 17:31
AndreaAndrea
1
answered Feb 5 at 17:31
AndreaAndrea
1
1
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f473031%2ferror-miktex-console-already-running%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
i,3Bujn,Bq3pjRX FoIxx7FqQbve5vpgnIJU vDfq7,EYqSOf sZ3MwMWco,dsZsTVkrgZQNnUPdSYe
1
Maybe tex.stackexchange.com/questions/443378/… gives some hints.
– albert
Feb 2 at 14:33