# Pkg.update fails on windows 7 with private repository

**URL:** https://discourse.julialang.org/t/pkg-update-fails-on-windows-7-with-private-repository/10282
**Category:** General Usage
**Created:** [April 11, 2018, 1:28pm UTC](https://discourse.julialang.org/t/pkg-update-fails-on-windows-7-with-private-repository/10282 "2018-04-11T13:28:19Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![spuhlerd](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@spuhlerd](https://discourse.julialang.org/u/spuhlerd)
#### Post date: [April 11, 2018, 1:28pm UTC](https://discourse.julialang.org/t/pkg-update-fails-on-windows-7-with-private-repository/10282/1 "2018-04-11T13:28:19Z")

</div>

Hi everyone,

I’m have a private package on GitLab. When I run `Pkg.update()` Julia is asking for the credentials of this repository. This works fine on Linux and Windows 10, however causes Julia to crash on Windows 7 Enterprise.

A “Windows Security” window opens. After the credentials are entered Julia exits without error message. The error occurs when Julia is started from the command line, git bash, or Atom.

 ![image](https://global.discourse-cdn.com/julialang/original/3X/0/4/042045d75e8f4121ff58190823e517c7833ce80e.png)

Does anybody has a recommendation fro a work around?

Many thanks,  
Dorothee

julia```  
julia\> versioninfo()  
Julia Version 0.6.2  
Commit d386e40c17\* (2017-12-13 18:08 UTC)  
Platform Info:  
OS: Windows (x86\_64-w64-mingw32)  
CPU: Intel(R) Core™ i7-4770 CPU @ 3.40GHz  
WORD\_SIZE: 64  
BLAS: libopenblas (USE64BITINT DYNAMIC\_ARCH NO\_AFFINITY Haswell)  
LAPACK: libopenblas64\_  
LIBM: libopenlibm  
LLVM: libLLVM-3.9.1 (ORCJIT, haswell)

```julia

```

---

<div class="post-metadata">

### Author: ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [April 11, 2018, 1:35pm UTC](https://discourse.julialang.org/t/pkg-update-fails-on-windows-7-with-private-repository/10282/2 "2018-04-11T13:35:45Z")

</div>

Make sure your ssh keys are in order:

> **[Use SSH keys to communicate with GitLab | GitLab](https://docs.gitlab.com/ee/user/ssh.html)**
>
> Documentation for GitLab Community Edition, GitLab Enterprise Edition, Omnibus GitLab, and GitLab Runner.

Then use the `ssh` protocol for the repository, instead of `https`. Eg change the remote, or clone starting with that.

---

<div class="post-metadata">

### Author: ![spuhlerd](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@spuhlerd](https://discourse.julialang.org/u/spuhlerd)
#### Post date: [April 12, 2018, 7:59pm UTC](https://discourse.julialang.org/t/pkg-update-fails-on-windows-7-with-private-repository/10282/3 "2018-04-12T19:59:18Z")

</div>

Hi, thank you for your suggestion!  
I uploaded my ssh key and changed the remote. I can push and pull but when updating the Pkg I get this error:  
ERROR: Update finished with errors.  
=\> Package SanitationSystemMassFlow cannot be updated.  
GitError(Code:ERROR, Class:SSH, Failed to start SSH session: Unable to exchange encryption keys)

Any suggestions?  
Dorothee

---

<div class="post-metadata">

### Author: ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [April 13, 2018, 7:32am UTC](https://discourse.julialang.org/t/pkg-update-fails-on-windows-7-with-private-repository/10282/4 "2018-04-13T07:32:43Z")

</div>

I don’t use Windows so unfortunately I cannot help you with a more specific suggestion, but I would try this fix:

> [@Errors for Git / Pkg](https://discourse.julialang.org/t/errors-for-git-pkg/9351):
>
> There have been various reports of issues running package operations recently. They manifest as one of the following messages on running any package operations, such as Pkg.init or Pkg.add: ERROR: GitError(Code:ERROR, Class:Net, SSL error: error:1407742E:SSL routines:SSL23\_GET\_SERVER\_HELLO:tlsv1 alert protocol version) or ERROR: GitError(Code:ECERTIFICATE, Class:OS, user cancelled certificate check: ) This is happening because GitHub stopped supporting TLS 1.0 in February: The error occu…
