# Persistent EPERM error (operation not permitted, rmdir) during homey app run/build on Windows 11

**URL:** <https://community.homey.app/t/persistent-eperm-error-operation-not-permitted-rmdir-during-homey-app-run-build-on-windows-11/134444>\
**Category:** Developers\
**Tags:** app, zigbee, homey-pro\
**Created:** [April 11, 2025, 2:42am UTC](https://community.homey.app/t/persistent-eperm-error-operation-not-permitted-rmdir-during-homey-app-run-build-on-windows-11/134444 "2025-04-11T02:42:39Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ArneB](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arneb/32/131867_2.png) [@ArneB](https://community.homey.app/u/ArneB)\
**Post date:** [April 13, 2025, 4:33pm UTC](https://community.homey.app/t/persistent-eperm-error-operation-not-permitted-rmdir-during-homey-app-run-build-on-windows-11/134444/3 "2025-04-13T16:33:44Z")

</div>

Thanks! I solved this and have a new problem:  
[SDKv3 Zigbee Device (ZigbeeDevice) Fails to Initialize (onNodeInit/Constructor Not Called) After Successful Driver Match via CLI run --remote (ID Lock / Datek) - Developers - Homey Community Forum](https://community.homey.app/t/sdkv3-zigbee-device-zigbeedevice-fails-to-initialize-onnodeinit-constructor-not-called-after-successful-driver-match-via-cli-run-remote-id-lock-datek/134590)

---

_[View the full topic](https://community.homey.app/t/persistent-eperm-error-operation-not-permitted-rmdir-during-homey-app-run-build-on-windows-11/134444)._