Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo unable to find the file

Build is running as a Remote Agent (Windows Server 2012) and the Remote Agent is running as a service and configured with correct Log on Account. The EXE 'streams.exe' is placed inside the path "C:\Windows\System32" and this path is mentioned under the system variable.


Just to cross verify, in the bamboo plan, I have executed the command "echo %PATH%" and I can confirm the path "C:\Windows\System32" is present. But when I call the command streams.exe in my bamboo plan it gives the below error message.


streams.exe is not recognized as an internal or external command

I have verified many times that the file is present inside the path "C:\Windows\System32" on the Remote Agent. To further troubleshoot the issue, in the Bamboo Plan, I have given the below commands.


cd C:\Windows\System32

dir /s /b streams.exe


But it gives "File Not Found".

When the file is present in the machine why Bamboo cannot list it?

1 answer

1 vote
Minh Tran Atlassian Team Jan 09, 2020

@karthickmurugadhas Can you try to move streams.exe to another folder under a user folder and add that folder to PATH variable to see if that works for you?

Yes this works.  Any more details  of this behavior? I mean why Bamboo cannot pick/find files under C:\Windows\System32 when it is configured in PATH ?

Minh Tran Atlassian Team Jan 09, 2020

I thought, it probably limits to access to system folder in order to protect agents

Normal practice, we should leave our custom executable in our custom folders instead of leaving there

Minh Tran Atlassian Team Jan 09, 2020

@karthickmurugadhas Can you accept the answer if that works for you? So other people having the same problem will benefit from it

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events