# Can't deploy everytime I add any modification

**URL:** <https://discourse.nodered.org/t/cant-deploy-everytime-i-add-any-modification/8817>\
**Category:** General\
**Created:** [10 March 2019 22:28 UTC](https://discourse.nodered.org/t/cant-deploy-everytime-i-add-any-modification/8817 "2019-03-10T22:28:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nassima100](https://avatars.discourse-cdn.com/v4/letter/n/e5b9ba/32.png) [@nassima100](https://discourse.nodered.org/u/nassima100)\
**Post date:** [10 March 2019 22:28 UTC](https://discourse.nodered.org/t/cant-deploy-everytime-i-add-any-modification/8817/1 "2019-03-10T22:28:30Z")

</div>

Hello, does anyone know why I'm having this error each time I add or modifiy a node or a flow ?

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/d/d44072280861ed8d140067f4fe3fb24e24827ef4.png)

---

<div class="post-metadata">

**Author:** ![nassima100](https://avatars.discourse-cdn.com/v4/letter/n/e5b9ba/32.png) [@nassima100](https://discourse.nodered.org/u/nassima100)\
**Post date:** [10 March 2019 22:39 UTC](https://discourse.nodered.org/t/cant-deploy-everytime-i-add-any-modification/8817/2 "2019-03-10T22:39:19Z")

</div>

I found it, I should've launched node-red from an administrative command prompt and not from just a cmd

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [11 March 2019 08:18 UTC](https://discourse.nodered.org/t/cant-deploy-everytime-i-add-any-modification/8817/3 "2019-03-11T08:18:56Z")

</div>

I don't use Windows, but I am fairly sure that your .node-red folder should not be in that location. The Program Files folder is for programs not user data. I imagine the reason you are having to run as administrator (which is not a good idea, I think) is because it is in that location. Hopefully someone (@dceejay?) will advise what you should do. Or perhaps advise that I am talking rubbish.

---

<div class="post-metadata">

**Author:** ![nassima100](https://avatars.discourse-cdn.com/v4/letter/n/e5b9ba/32.png) [@nassima100](https://discourse.nodered.org/u/nassima100)\
**Post date:** [11 March 2019 13:11 UTC](https://discourse.nodered.org/t/cant-deploy-everytime-i-add-any-modification/8817/4 "2019-03-11T13:11:12Z")

</div>

I'll take it in consideration thank you.

---

<div class="post-metadata">

**Author:** ![Andrei](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andrei/32/10446_2.png) [@Andrei](https://discourse.nodered.org/u/Andrei)\
**Post date:** [12 March 2019 03:04 UTC](https://discourse.nodered.org/t/cant-deploy-everytime-i-add-any-modification/8817/5 "2019-03-12T03:04:36Z")

</div>

Hi @nassima100, I faced the very same issue today. As a workaround I renamed the suspicious file `.flow.json.backup` in my case, to another random name. After this action, it was possible to deploy the flow. A new backup file was created automatically. I am not sure why this happened but I suspect it may be related to the activation of Google drive sync in the project folder. This was the only change I did recently in my system. Eventually, it may be a result of some unsolicited Windows10 upgrade, who knows.

 ![r-01](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/0/0dc452b34c97ac549ac68a6db51f9c6e84762013.png)

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [12 March 2019 07:46 UTC](https://discourse.nodered.org/t/cant-deploy-everytime-i-add-any-modification/8817/6 "2019-03-12T07:46:33Z")

</div>

@Andrei Node-RED creates that backup file each time you deploy. Nothing to do with Windows.

The original issue here was simply one of permissions having run Node-RED as a different user.