# Persisted workspace missing on Windows

**URL:** <https://discuss.circleci.com/t/persisted-workspace-missing-on-windows/33473>\
**Category:** Build Environment\
**Created:** [November 21, 2019, 12:21am UTC](https://discuss.circleci.com/t/persisted-workspace-missing-on-windows/33473 "2019-11-21T00:21:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![christhegrand](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/christhegrand/32/23292_2.png) [@christhegrand](https://discuss.circleci.com/u/christhegrand)\
**Post date:** [November 21, 2019, 12:21am UTC](https://discuss.circleci.com/t/persisted-workspace-missing-on-windows/33473/1 "2019-11-21T00:21:15Z")

</div>

Hi there,  
We’re trying to build our Electron app on the win/vs2019 executor with bash.exe. As part of our job, we call attach\_workspace and attach the workspace at /tmp/env. The content that should have been persisted to that directory is not there on Windows, though - /tmp exists but /tmp/env does not. The workspace contents are accessible by all of our other jobs, which are running on various Linux or MacOS images. Is there something additional I need to do in order to attach our workspace under a Windows image?

Thanks,  
Chris