# Unable to update vagrant dev install on Windows

**URL:** https://meta.discourse.org/t/unable-to-update-vagrant-dev-install-on-windows/64383
**Category:** Development
**Created:** [2017年六月12日 20:29 UTC](https://meta.discourse.org/t/unable-to-update-vagrant-dev-install-on-windows/64383 "2017-06-12T20:29:33Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [2017年六月12日 20:29 UTC](https://meta.discourse.org/t/unable-to-update-vagrant-dev-install-on-windows/64383/1 "2017-06-12T20:29:33Z")

</div>

I’m getting the following error when attempting to update my dev install on Windows. I first did a `git pull`, then `vagrant up`, `vagrant ssh`, and finally `bundle install`. The error occurs when trying to run `bundle exec rake db:migrate`

```plaintext
vagrant@discourse:/vagrant$ bundle exec rake db:migrate
rake aborted!
ln: failed to create symbolic link '/vagrant/public/plugins/discourse-narrative-bot': Protocol error
/vagrant/lib/discourse.rb:26:in `execute_command'
/vagrant/lib/plugin/instance.rb:368:in `activate!'
/vagrant/lib/discourse.rb:126:in `block in activate_plugins!'
/vagrant/lib/discourse.rb:123:in `each'
/vagrant/lib/discourse.rb:123:in `activate_plugins!'
/vagrant/config/application.rb:179:in `<class:Application>'
/vagrant/config/application.rb:27:in `<module:Discourse>'
/vagrant/config/application.rb:26:in `<top (required)>'
/vagrant/rakefile:5:in `require'
/vagrant/rakefile:5:in `<top (required)>'
/home/vagrant/.rvm/gems/ruby-2.3.1/gems/rake-12.0.0/exe/rake:27:in `<top (required)>'
/home/vagrant/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `eval'
/home/vagrant/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `<main>'
(See full trace by running task with --trace)

```

---

<div class="post-metadata">

### Author: ![blake](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/blake/32/157322_2.png) [@blake](https://meta.discourse.org/u/blake)
#### Post date: [2017年六月12日 21:28 UTC](https://meta.discourse.org/t/unable-to-update-vagrant-dev-install-on-windows/64383/2 "2017-06-12T21:28:02Z")

</div>

Looks like its related to this line:

> [@jomaxro](#):
>
> ln: failed to create symbolic link ‘/vagrant/public/plugins/discourse-narrative-bot’: Protocol error

Did you already install the discobot plugin before this? Do we normally create symlinks or is that a vagrant thing?

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [2017年六月12日 21:28 UTC](https://meta.discourse.org/t/unable-to-update-vagrant-dev-install-on-windows/64383/3 "2017-06-12T21:28:53Z")

</div>

> [@blake](#):
>
> Did you already install the discobot plugin before this?

Nope, haven’t updated in quite some time. Also never installed plugins in Vagrant.

> [@blake](#):
>
> Do we normally create symlinks or is that a vagrant thing?

I have no idea…

---

<div class="post-metadata">

### Author: ![blake](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/blake/32/157322_2.png) [@blake](https://meta.discourse.org/u/blake)
#### Post date: [2017年六月12日 21:31 UTC](https://meta.discourse.org/t/unable-to-update-vagrant-dev-install-on-windows/64383/4 "2017-06-12T21:31:18Z")

</div>

Can you just try creating a test symlink yourself and see if it works?

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [2017年六月12日 21:33 UTC](https://meta.discourse.org/t/unable-to-update-vagrant-dev-install-on-windows/64383/5 "2017-06-12T21:33:46Z")

</div>

It does not appear to be working:

```bash
vagrant@discourse:/vagrant$ touch temp
vagrant@discourse:/vagrant$ ln -s temp temp-link
ln: failed to create symbolic link 'temp-link': Protocol error
vagrant@discourse:/vagrant$

```

---

<div class="post-metadata">

### Author: ![blake](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/blake/32/157322_2.png) [@blake](https://meta.discourse.org/u/blake)
#### Post date: [2017年六月12日 21:34 UTC](https://meta.discourse.org/t/unable-to-update-vagrant-dev-install-on-windows/64383/6 "2017-06-12T21:34:41Z")

</div>

check this out

[https://github.com/mitchellh/vagrant/issues/6024](https://github.com/mitchellh/vagrant/issues/6024)

I didn’t read the whole thing, but you might need to downgrade to a different version of vagrant if they haven’t fixed it yet.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年六月13日 14:37 UTC](https://meta.discourse.org/t/unable-to-update-vagrant-dev-install-on-windows/64383/7 "2017-06-13T14:37:30Z")

</div>

I would recommend avoiding vagrant, if you need a “quick” setup just start an ubuntu VM and and use our docker dev env.

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [2017年六月13日 16:26 UTC](https://meta.discourse.org/t/unable-to-update-vagrant-dev-install-on-windows/64383/8 "2017-06-13T16:26:12Z")

</div>

Sounds good Sam - will test that out later today.

---

<div class="post-metadata">

### Author: ![epitome](https://avatars.discourse-cdn.com/v4/letter/e/3ec8ea/32.png) [@epitome](https://meta.discourse.org/u/epitome)
#### Post date: [2017年十月2日 23:18 UTC](https://meta.discourse.org/t/unable-to-update-vagrant-dev-install-on-windows/64383/9 "2017-10-02T23:18:31Z")

</div>

you need special rights to create symbolic links with windows (inside virtual machines), the right goes by “SeCreateSymbolicLink”.  
Administrator have this right by default. When you run vagrant up/ssh, you need to run it with a user that has this right.

I avoided this error by starting a powershell as administrator (since I didn’t want to bother with granting rights to my user) and discourse is up and running
