<commit_before>[<-- Back to main section](../README.md)

# Troubleshooting

## Startup or update errors

You can safely reprovision your VM:

```bash

# if box is NOT started
vagrant up --provision

# if box is already started
vagrant provision
```
<commit_msg>Adds Windows 10 VMWare Workaround to TROUBLESHOOTING<commit_after>[<-- Back to main section](../README.md)

# Troubleshooting

## Startup or update errors

### Reprovision the VM

You can safely reprovision your VM:

```bash

# if box is NOT started
vagrant up --provision

# if box is already started
vagrant provision
```

### Windows 10 and VMWare

It can happen that the **Virtual Network Adapters** (in this case host only adapter)
break **on every shutdown** or **disconnect** vom Network.

Windows 10 has **currently issues with Virtual Networks** on different VM Softwares.
With VMWare a Workaround can be reseeting the Network Adapters right before
starting the VM.

1. Shut Down the VM (if not down already)
2. Open VMWare
3. Open in Menu: **Edit > Virtual Network Editor...**
4. Request Admin Rights in this Window (if not already started with them)
5. Click: **Restore Defaults**

This will reset all virtual Network Adapters.
If you now start Vagrant with **vagrant up**, the required Adapters will be
recreated.
{'fraction_non_alphanumeric': 0.08786936236391912, 'fraction_numerical': 0.008553654743390357, 'mean_word_length': 4.274590163934426, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 4, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7226641', 'n_tokens_mistral': 403, 'n_tokens_neox': 376, 'n_words': 184}