The solution to this is to upgrade to Win 10 1809. But I won't just upgrade win 10 (and have updates off) because as we all know, these recent updates usually mess things up. And 1803 works fine for me so I will pass on forced updates. The issue seems to be WB trying to access itself twice through MO2. The problem also is not a WB problem but an MO2 issue. To use the workaround you will need a file unlocker. I use LockHunter (https://lockhunter.com/). Install this program or use what you like. 1. Launch WB out of MO2 to make sure it works. If you are sure it does skip this. 2. Launch WB from MO2 3. When the 'Folder in Use' message pops up (pay attention to its name which should be WryeBash_XXXXX) go to C:\Users\USER\AppData\Local\Temp\WryeBash_XXXXX 4. Right click on the folder and you will get a context menu. Look for 'Whats locking this folder' You will see a window and in that window it will say 'What processes are locking this folder' You will see WB listed. 5. Click on Wrye Bash.exe and press the 'Unlock It!' button. It will ask for confirmation, hit yes. Once its unlock you can close this window. 6. Go back to the 'Folder in Use' window and press Try Again. 7. WB will launch. Note if you make a bashed patch, you will get a folder in use when it copies the document out of the temp file.. you can just hit cancel at the end of the bashed patch, it seems to copy the document and bashed patch file to overwrite fine. There might be a better way or a true fix but this worked for me with both SSE and FO4. Hopefully it works for you also.
