MikTeX update error
Update of my MikTeX portable on Win 7 failed this morning (Dec 24th, 2016). The error message is given below. Prior to that a lot of packages have been removed, obviously some critical ones among them as well. My offline DB was syncronized. Was my update too early or what might be the cause?
miktex miktex-update
asked Dec 24 '16 at 9:55
tfrantfran
26113
add a comment |
Update of my MikTeX portable on Win 7 failed this morning (Dec 24th, 2016). The error message is given below. Prior to that a lot of packages have been removed, obviously some critical ones among them as well. My offline DB was syncronized. Was my update too early or what might be the cause?
miktex miktex-update
asked Dec 24 '16 at 9:55
tfrantfran
26113
When did you the update before this one?
– Ulrike Fischer
Dec 24 '16 at 11:17
Try uninstalling MiKTeX and then reinstalling it.
– user 170039
Dec 24 '16 at 13:52
It looks as if you can't start the update manager GUI. Try to call it from the command line in the trash-menu of miktex portable. See also my comment here sourceforge.net/p/miktex/bugs/2546/#7751 (don't use the--repository-release-state=nextoption).
– Ulrike Fischer
Dec 24 '16 at 13:58
add a comment |
Update of my MikTeX portable on Win 7 failed this morning (Dec 24th, 2016). The error message is given below. Prior to that a lot of packages have been removed, obviously some critical ones among them as well. My offline DB was syncronized. Was my update too early or what might be the cause?
miktex miktex-update
asked Dec 24 '16 at 9:55
tfrantfran
26113
Update of my MikTeX portable on Win 7 failed this morning (Dec 24th, 2016). The error message is given below. Prior to that a lot of packages have been removed, obviously some critical ones among them as well. My offline DB was syncronized. Was my update too early or what might be the cause?
miktex miktex-update
miktex miktex-update
asked Dec 24 '16 at 9:55
tfrantfran
26113
asked Dec 24 '16 at 9:55
tfrantfran
26113
asked Dec 24 '16 at 9:55
tfrantfran
26113
asked Dec 24 '16 at 9:55
tfrantfran
26113
asked Dec 24 '16 at 9:55
tfrantfran
26113
26113
When did you the update before this one?
– Ulrike Fischer
Dec 24 '16 at 11:17
Try uninstalling MiKTeX and then reinstalling it.
– user 170039
Dec 24 '16 at 13:52
It looks as if you can't start the update manager GUI. Try to call it from the command line in the trash-menu of miktex portable. See also my comment here sourceforge.net/p/miktex/bugs/2546/#7751 (don't use the--repository-release-state=nextoption).
– Ulrike Fischer
Dec 24 '16 at 13:58
add a comment |
When did you the update before this one?
– Ulrike Fischer
Dec 24 '16 at 11:17
Try uninstalling MiKTeX and then reinstalling it.
– user 170039
Dec 24 '16 at 13:52
It looks as if you can't start the update manager GUI. Try to call it from the command line in the trash-menu of miktex portable. See also my comment here sourceforge.net/p/miktex/bugs/2546/#7751 (don't use the--repository-release-state=nextoption).
– Ulrike Fischer
Dec 24 '16 at 13:58
When did you the update before this one?
– Ulrike Fischer
Dec 24 '16 at 11:17
When did you the update before this one?
– Ulrike Fischer
Dec 24 '16 at 11:17
Try uninstalling MiKTeX and then reinstalling it.
– user 170039
Dec 24 '16 at 13:52
Try uninstalling MiKTeX and then reinstalling it.
– user 170039
Dec 24 '16 at 13:52
It looks as if you can't start the update manager GUI. Try to call it from the command line in the trash-menu of miktex portable. See also my comment here sourceforge.net/p/miktex/bugs/2546/#7751 (don't use the
--repository-release-state=next option).– Ulrike Fischer
Dec 24 '16 at 13:58
It looks as if you can't start the update manager GUI. Try to call it from the command line in the trash-menu of miktex portable. See also my comment here sourceforge.net/p/miktex/bugs/2546/#7751 (don't use the
--repository-release-state=next option).– Ulrike Fischer
Dec 24 '16 at 13:58
add a comment |
6 Answers
6
active
oldest
votes
Analyzing mpm logs and miktex sources gives a hint that MiKTeX Update Manager incorrectly handles a situation when no proxy is set. So I entered the proxy (Connections Settings... button) (I used uk11.frigate.org), after which the update process worked.
answered Dec 24 '16 at 23:32
stu003stu003
1664
I just should add that this procedure worked for me with both a 32-bit portable and 64-bit stationary installation.
– stu003
Dec 24 '16 at 23:48
3
Once this has been done, you don't need the proxy settings anymore and it seems to fix itself after the one update of doom.
– Samuel Albert
Jan 1 '17 at 17:19
1
This worked for me, too. And the proxy settings can be removed after that. Thanks.
– Arzigoglu
Jan 4 '17 at 8:48
add a comment |
I had a similar problem this morning (1st: update of the system -> went fine; then update of the packages with error as above) and tried answer 2 (proxy setting). As I have no proxy, I just checked and unchecked the box. Then tried "let me choose repository" and manually selected one. After this the update worked.
P.S. There was an error messages at the end "executed process did not succed", but there seem to be no furtehr update.
Update: There seems to be a problem with the "nearest site selection" Maintainance "Update formats" needed to load multiple packages, which also only worked after manually selecting repository.
answered Dec 26 '16 at 10:28
Werner A.Werner A.
512
2
I can confirm that this worked for me. I was getting the same error as reported by the OP after the second update, and the fix was to click "Connection Settings" and then tick the box "Use a proxy server" and then immediately untick it again. Afterwards, I was able to proceed through the wizard as usual.
– Andrew Bate
Jan 3 '17 at 0:53
add a comment |
The same has happened to me today. I fixed the issue doing the following steps:
- Uninstall MiKTeX completely (after uninstalling from the Control Panel, I had to manually delete the folder in Program Files, for some reason).
- Install using the basic installer.
- Run MiKTeX Update.
- Run MiKTeX Update (once again, yes, first time it will allow you to install just some basic updates).
- Compile the document.
This is what has worked for me so far. I have left the on-the-fly package install as "ask me first".
Note: After step 2 I tried compiling directly, but after installing the required packages I got incompatibilities between biber and biblatex.
answered Dec 24 '16 at 17:46
IsaacIsaac
286
add a comment |
Updating an old MiKTeX installation or installing the current basic-miktex-2.9.6161 and updating it leads to the described error. (Such things should never happen, but it is not the first time.) The suggested deinstall + reinstall does not help.
The combination of packages in the 2016-12-23 repos seems to be broken (at least for some systems). I suggest: Do not update and wait for another release.
As of 2017-01-05, MiKTeX.org writes:
MiKTeX Update Wizard issues
Last edited: 1/5/2017 10:06:29 AM
The latest Version of the update wizard has issues on some Windows Systems.
The problem has been identified and a fix is available here:
https://ctan.org/tex-archive/systems/win32/miktex/support/update
Update
A few days later, the next version of MikTeX worked again.
answered Dec 24 '16 at 15:45
OneOne
9751117
add a comment |
I was also experiencing the update - the reason was I had a document opened and a compilation in progress:-D simply stop it and close the MikTeX then check for updates from any random source.
answered 6 hours ago
PatrykOsPatrykOs
191
New contributor
PatrykOs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Note this is not a fix for the original error message (shown in question) i.e. a connection error MiKTeX will tell you off by means of a very explanatory error message for trying to update open files.
– KJO
2 hours ago
add a comment |
I had the same problem on one of my machines. Running the update from a DOS prompt worked. After that, I tried checking and unchecking the proxy box as suggested in one of the earlier answers. After that, the update wizard works again.
answered Dec 27 '16 at 15:52
Michael RenardyMichael Renardy
101
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%2f345485%2fmiktex-update-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
Analyzing mpm logs and miktex sources gives a hint that MiKTeX Update Manager incorrectly handles a situation when no proxy is set. So I entered the proxy (Connections Settings... button) (I used uk11.frigate.org), after which the update process worked.
answered Dec 24 '16 at 23:32
stu003stu003
1664
I just should add that this procedure worked for me with both a 32-bit portable and 64-bit stationary installation.
– stu003
Dec 24 '16 at 23:48
3
Once this has been done, you don't need the proxy settings anymore and it seems to fix itself after the one update of doom.
– Samuel Albert
Jan 1 '17 at 17:19
1
This worked for me, too. And the proxy settings can be removed after that. Thanks.
– Arzigoglu
Jan 4 '17 at 8:48
add a comment |
Analyzing mpm logs and miktex sources gives a hint that MiKTeX Update Manager incorrectly handles a situation when no proxy is set. So I entered the proxy (Connections Settings... button) (I used uk11.frigate.org), after which the update process worked.
answered Dec 24 '16 at 23:32
stu003stu003
1664
I just should add that this procedure worked for me with both a 32-bit portable and 64-bit stationary installation.
– stu003
Dec 24 '16 at 23:48
3
Once this has been done, you don't need the proxy settings anymore and it seems to fix itself after the one update of doom.
– Samuel Albert
Jan 1 '17 at 17:19
1
This worked for me, too. And the proxy settings can be removed after that. Thanks.
– Arzigoglu
Jan 4 '17 at 8:48
add a comment |
Analyzing mpm logs and miktex sources gives a hint that MiKTeX Update Manager incorrectly handles a situation when no proxy is set. So I entered the proxy (Connections Settings... button) (I used uk11.frigate.org), after which the update process worked.
answered Dec 24 '16 at 23:32
stu003stu003
1664
Analyzing mpm logs and miktex sources gives a hint that MiKTeX Update Manager incorrectly handles a situation when no proxy is set. So I entered the proxy (Connections Settings... button) (I used uk11.frigate.org), after which the update process worked.
answered Dec 24 '16 at 23:32
stu003stu003
1664
answered Dec 24 '16 at 23:32
stu003stu003
1664
answered Dec 24 '16 at 23:32
stu003stu003
1664
answered Dec 24 '16 at 23:32
stu003stu003
1664
1664
I just should add that this procedure worked for me with both a 32-bit portable and 64-bit stationary installation.
– stu003
Dec 24 '16 at 23:48
3
Once this has been done, you don't need the proxy settings anymore and it seems to fix itself after the one update of doom.
– Samuel Albert
Jan 1 '17 at 17:19
1
This worked for me, too. And the proxy settings can be removed after that. Thanks.
– Arzigoglu
Jan 4 '17 at 8:48
add a comment |
I just should add that this procedure worked for me with both a 32-bit portable and 64-bit stationary installation.
– stu003
Dec 24 '16 at 23:48
3
Once this has been done, you don't need the proxy settings anymore and it seems to fix itself after the one update of doom.
– Samuel Albert
Jan 1 '17 at 17:19
1
This worked for me, too. And the proxy settings can be removed after that. Thanks.
– Arzigoglu
Jan 4 '17 at 8:48
I just should add that this procedure worked for me with both a 32-bit portable and 64-bit stationary installation.
– stu003
Dec 24 '16 at 23:48
I just should add that this procedure worked for me with both a 32-bit portable and 64-bit stationary installation.
– stu003
Dec 24 '16 at 23:48
3
3
Once this has been done, you don't need the proxy settings anymore and it seems to fix itself after the one update of doom.
– Samuel Albert
Jan 1 '17 at 17:19
Once this has been done, you don't need the proxy settings anymore and it seems to fix itself after the one update of doom.
– Samuel Albert
Jan 1 '17 at 17:19
1
1
This worked for me, too. And the proxy settings can be removed after that. Thanks.
– Arzigoglu
Jan 4 '17 at 8:48
This worked for me, too. And the proxy settings can be removed after that. Thanks.
– Arzigoglu
Jan 4 '17 at 8:48
add a comment |
I had a similar problem this morning (1st: update of the system -> went fine; then update of the packages with error as above) and tried answer 2 (proxy setting). As I have no proxy, I just checked and unchecked the box. Then tried "let me choose repository" and manually selected one. After this the update worked.
P.S. There was an error messages at the end "executed process did not succed", but there seem to be no furtehr update.
Update: There seems to be a problem with the "nearest site selection" Maintainance "Update formats" needed to load multiple packages, which also only worked after manually selecting repository.
answered Dec 26 '16 at 10:28
Werner A.Werner A.
512
2
I can confirm that this worked for me. I was getting the same error as reported by the OP after the second update, and the fix was to click "Connection Settings" and then tick the box "Use a proxy server" and then immediately untick it again. Afterwards, I was able to proceed through the wizard as usual.
– Andrew Bate
Jan 3 '17 at 0:53
add a comment |
I had a similar problem this morning (1st: update of the system -> went fine; then update of the packages with error as above) and tried answer 2 (proxy setting). As I have no proxy, I just checked and unchecked the box. Then tried "let me choose repository" and manually selected one. After this the update worked.
P.S. There was an error messages at the end "executed process did not succed", but there seem to be no furtehr update.
Update: There seems to be a problem with the "nearest site selection" Maintainance "Update formats" needed to load multiple packages, which also only worked after manually selecting repository.
answered Dec 26 '16 at 10:28
Werner A.Werner A.
512
2
I can confirm that this worked for me. I was getting the same error as reported by the OP after the second update, and the fix was to click "Connection Settings" and then tick the box "Use a proxy server" and then immediately untick it again. Afterwards, I was able to proceed through the wizard as usual.
– Andrew Bate
Jan 3 '17 at 0:53
add a comment |
I had a similar problem this morning (1st: update of the system -> went fine; then update of the packages with error as above) and tried answer 2 (proxy setting). As I have no proxy, I just checked and unchecked the box. Then tried "let me choose repository" and manually selected one. After this the update worked.
P.S. There was an error messages at the end "executed process did not succed", but there seem to be no furtehr update.
Update: There seems to be a problem with the "nearest site selection" Maintainance "Update formats" needed to load multiple packages, which also only worked after manually selecting repository.
answered Dec 26 '16 at 10:28
Werner A.Werner A.
512
I had a similar problem this morning (1st: update of the system -> went fine; then update of the packages with error as above) and tried answer 2 (proxy setting). As I have no proxy, I just checked and unchecked the box. Then tried "let me choose repository" and manually selected one. After this the update worked.
P.S. There was an error messages at the end "executed process did not succed", but there seem to be no furtehr update.
Update: There seems to be a problem with the "nearest site selection" Maintainance "Update formats" needed to load multiple packages, which also only worked after manually selecting repository.
answered Dec 26 '16 at 10:28
Werner A.Werner A.
512
answered Dec 26 '16 at 10:28
Werner A.Werner A.
512
answered Dec 26 '16 at 10:28
Werner A.Werner A.
512
answered Dec 26 '16 at 10:28
Werner A.Werner A.
512
512
2
I can confirm that this worked for me. I was getting the same error as reported by the OP after the second update, and the fix was to click "Connection Settings" and then tick the box "Use a proxy server" and then immediately untick it again. Afterwards, I was able to proceed through the wizard as usual.
– Andrew Bate
Jan 3 '17 at 0:53
add a comment |
2
I can confirm that this worked for me. I was getting the same error as reported by the OP after the second update, and the fix was to click "Connection Settings" and then tick the box "Use a proxy server" and then immediately untick it again. Afterwards, I was able to proceed through the wizard as usual.
– Andrew Bate
Jan 3 '17 at 0:53
2
2
I can confirm that this worked for me. I was getting the same error as reported by the OP after the second update, and the fix was to click "Connection Settings" and then tick the box "Use a proxy server" and then immediately untick it again. Afterwards, I was able to proceed through the wizard as usual.
– Andrew Bate
Jan 3 '17 at 0:53
I can confirm that this worked for me. I was getting the same error as reported by the OP after the second update, and the fix was to click "Connection Settings" and then tick the box "Use a proxy server" and then immediately untick it again. Afterwards, I was able to proceed through the wizard as usual.
– Andrew Bate
Jan 3 '17 at 0:53
add a comment |
The same has happened to me today. I fixed the issue doing the following steps:
- Uninstall MiKTeX completely (after uninstalling from the Control Panel, I had to manually delete the folder in Program Files, for some reason).
- Install using the basic installer.
- Run MiKTeX Update.
- Run MiKTeX Update (once again, yes, first time it will allow you to install just some basic updates).
- Compile the document.
This is what has worked for me so far. I have left the on-the-fly package install as "ask me first".
Note: After step 2 I tried compiling directly, but after installing the required packages I got incompatibilities between biber and biblatex.
answered Dec 24 '16 at 17:46
IsaacIsaac
286
add a comment |
The same has happened to me today. I fixed the issue doing the following steps:
- Uninstall MiKTeX completely (after uninstalling from the Control Panel, I had to manually delete the folder in Program Files, for some reason).
- Install using the basic installer.
- Run MiKTeX Update.
- Run MiKTeX Update (once again, yes, first time it will allow you to install just some basic updates).
- Compile the document.
This is what has worked for me so far. I have left the on-the-fly package install as "ask me first".
Note: After step 2 I tried compiling directly, but after installing the required packages I got incompatibilities between biber and biblatex.
answered Dec 24 '16 at 17:46
IsaacIsaac
286
add a comment |
The same has happened to me today. I fixed the issue doing the following steps:
- Uninstall MiKTeX completely (after uninstalling from the Control Panel, I had to manually delete the folder in Program Files, for some reason).
- Install using the basic installer.
- Run MiKTeX Update.
- Run MiKTeX Update (once again, yes, first time it will allow you to install just some basic updates).
- Compile the document.
This is what has worked for me so far. I have left the on-the-fly package install as "ask me first".
Note: After step 2 I tried compiling directly, but after installing the required packages I got incompatibilities between biber and biblatex.
answered Dec 24 '16 at 17:46
IsaacIsaac
286
The same has happened to me today. I fixed the issue doing the following steps:
- Uninstall MiKTeX completely (after uninstalling from the Control Panel, I had to manually delete the folder in Program Files, for some reason).
- Install using the basic installer.
- Run MiKTeX Update.
- Run MiKTeX Update (once again, yes, first time it will allow you to install just some basic updates).
- Compile the document.
This is what has worked for me so far. I have left the on-the-fly package install as "ask me first".
Note: After step 2 I tried compiling directly, but after installing the required packages I got incompatibilities between biber and biblatex.
answered Dec 24 '16 at 17:46
IsaacIsaac
286
edited Dec 24 '16 at 17:53
answered Dec 24 '16 at 17:46
IsaacIsaac
286
answered Dec 24 '16 at 17:46
IsaacIsaac
286
answered Dec 24 '16 at 17:46
IsaacIsaac
286
286
add a comment |
add a comment |
Updating an old MiKTeX installation or installing the current basic-miktex-2.9.6161 and updating it leads to the described error. (Such things should never happen, but it is not the first time.) The suggested deinstall + reinstall does not help.
The combination of packages in the 2016-12-23 repos seems to be broken (at least for some systems). I suggest: Do not update and wait for another release.
As of 2017-01-05, MiKTeX.org writes:
MiKTeX Update Wizard issues
Last edited: 1/5/2017 10:06:29 AM
The latest Version of the update wizard has issues on some Windows Systems.
The problem has been identified and a fix is available here:
https://ctan.org/tex-archive/systems/win32/miktex/support/update
Update
A few days later, the next version of MikTeX worked again.
answered Dec 24 '16 at 15:45
OneOne
9751117
add a comment |
Updating an old MiKTeX installation or installing the current basic-miktex-2.9.6161 and updating it leads to the described error. (Such things should never happen, but it is not the first time.) The suggested deinstall + reinstall does not help.
The combination of packages in the 2016-12-23 repos seems to be broken (at least for some systems). I suggest: Do not update and wait for another release.
As of 2017-01-05, MiKTeX.org writes:
MiKTeX Update Wizard issues
Last edited: 1/5/2017 10:06:29 AM
The latest Version of the update wizard has issues on some Windows Systems.
The problem has been identified and a fix is available here:
https://ctan.org/tex-archive/systems/win32/miktex/support/update
Update
A few days later, the next version of MikTeX worked again.
answered Dec 24 '16 at 15:45
OneOne
9751117
add a comment |
Updating an old MiKTeX installation or installing the current basic-miktex-2.9.6161 and updating it leads to the described error. (Such things should never happen, but it is not the first time.) The suggested deinstall + reinstall does not help.
The combination of packages in the 2016-12-23 repos seems to be broken (at least for some systems). I suggest: Do not update and wait for another release.
As of 2017-01-05, MiKTeX.org writes:
MiKTeX Update Wizard issues
Last edited: 1/5/2017 10:06:29 AM
The latest Version of the update wizard has issues on some Windows Systems.
The problem has been identified and a fix is available here:
https://ctan.org/tex-archive/systems/win32/miktex/support/update
Update
A few days later, the next version of MikTeX worked again.
answered Dec 24 '16 at 15:45
OneOne
9751117
Updating an old MiKTeX installation or installing the current basic-miktex-2.9.6161 and updating it leads to the described error. (Such things should never happen, but it is not the first time.) The suggested deinstall + reinstall does not help.
The combination of packages in the 2016-12-23 repos seems to be broken (at least for some systems). I suggest: Do not update and wait for another release.
As of 2017-01-05, MiKTeX.org writes:
MiKTeX Update Wizard issues
Last edited: 1/5/2017 10:06:29 AM
The latest Version of the update wizard has issues on some Windows Systems.
The problem has been identified and a fix is available here:
https://ctan.org/tex-archive/systems/win32/miktex/support/update
Update
A few days later, the next version of MikTeX worked again.
answered Dec 24 '16 at 15:45
OneOne
9751117
edited Mar 21 '17 at 18:08
answered Dec 24 '16 at 15:45
OneOne
9751117
answered Dec 24 '16 at 15:45
OneOne
9751117
answered Dec 24 '16 at 15:45
OneOne
9751117
9751117
add a comment |
add a comment |
I was also experiencing the update - the reason was I had a document opened and a compilation in progress:-D simply stop it and close the MikTeX then check for updates from any random source.
answered 6 hours ago
PatrykOsPatrykOs
191
New contributor
PatrykOs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Note this is not a fix for the original error message (shown in question) i.e. a connection error MiKTeX will tell you off by means of a very explanatory error message for trying to update open files.
– KJO
2 hours ago
add a comment |
I was also experiencing the update - the reason was I had a document opened and a compilation in progress:-D simply stop it and close the MikTeX then check for updates from any random source.
answered 6 hours ago
PatrykOsPatrykOs
191
New contributor
PatrykOs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Note this is not a fix for the original error message (shown in question) i.e. a connection error MiKTeX will tell you off by means of a very explanatory error message for trying to update open files.
– KJO
2 hours ago
add a comment |
I was also experiencing the update - the reason was I had a document opened and a compilation in progress:-D simply stop it and close the MikTeX then check for updates from any random source.
answered 6 hours ago
PatrykOsPatrykOs
191
New contributor
PatrykOs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I was also experiencing the update - the reason was I had a document opened and a compilation in progress:-D simply stop it and close the MikTeX then check for updates from any random source.
answered 6 hours ago
PatrykOsPatrykOs
191
New contributor
PatrykOs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 6 hours ago
PatrykOsPatrykOs
191
New contributor
PatrykOs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 6 hours ago
PatrykOsPatrykOs
191
answered 6 hours ago
PatrykOsPatrykOs
191
191
New contributor
PatrykOs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
PatrykOs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
PatrykOs is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Note this is not a fix for the original error message (shown in question) i.e. a connection error MiKTeX will tell you off by means of a very explanatory error message for trying to update open files.
– KJO
2 hours ago
add a comment |
Note this is not a fix for the original error message (shown in question) i.e. a connection error MiKTeX will tell you off by means of a very explanatory error message for trying to update open files.
– KJO
2 hours ago
Note this is not a fix for the original error message (shown in question) i.e. a connection error MiKTeX will tell you off by means of a very explanatory error message for trying to update open files.
– KJO
2 hours ago
Note this is not a fix for the original error message (shown in question) i.e. a connection error MiKTeX will tell you off by means of a very explanatory error message for trying to update open files.
– KJO
2 hours ago
add a comment |
I had the same problem on one of my machines. Running the update from a DOS prompt worked. After that, I tried checking and unchecking the proxy box as suggested in one of the earlier answers. After that, the update wizard works again.
answered Dec 27 '16 at 15:52
Michael RenardyMichael Renardy
101
add a comment |
I had the same problem on one of my machines. Running the update from a DOS prompt worked. After that, I tried checking and unchecking the proxy box as suggested in one of the earlier answers. After that, the update wizard works again.
answered Dec 27 '16 at 15:52
Michael RenardyMichael Renardy
101
add a comment |
I had the same problem on one of my machines. Running the update from a DOS prompt worked. After that, I tried checking and unchecking the proxy box as suggested in one of the earlier answers. After that, the update wizard works again.
answered Dec 27 '16 at 15:52
Michael RenardyMichael Renardy
101
I had the same problem on one of my machines. Running the update from a DOS prompt worked. After that, I tried checking and unchecking the proxy box as suggested in one of the earlier answers. After that, the update wizard works again.
answered Dec 27 '16 at 15:52
Michael RenardyMichael Renardy
101
answered Dec 27 '16 at 15:52
Michael RenardyMichael Renardy
101
answered Dec 27 '16 at 15:52
Michael RenardyMichael Renardy
101
answered Dec 27 '16 at 15:52
Michael RenardyMichael Renardy
101
101
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f345485%2fmiktex-update-error%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
When did you the update before this one?
– Ulrike Fischer
Dec 24 '16 at 11:17
Try uninstalling MiKTeX and then reinstalling it.
– user 170039
Dec 24 '16 at 13:52
It looks as if you can't start the update manager GUI. Try to call it from the command line in the trash-menu of miktex portable. See also my comment here sourceforge.net/p/miktex/bugs/2546/#7751 (don't use the
--repository-release-state=nextoption).– Ulrike Fischer
Dec 24 '16 at 13:58