Poor software development practices and support
RebusDrop for Windows installs in the user profile folder of the main administrator regardless what user account you use to install and what privileges it has, i.e. it's virtually unusable in most business environments.
Update (03/12/2026): -1 for their unhelpful reply dismissing the feedback instead of improving on it. If the installation path is a deliberate technical choice, it shouldn't be. It's a poor one that reveals laziness or ignorance and incompetence. It's unnecessary and doesn't ensure compatibility, correct permissions handling, nor stable operation across a wide range of Windows environments. If anything, installing in the user profile folder of the signed-in user would. Installing in the user profile folder of the main administrator account doesn't. On the contrary. It ensures the software can only be used by the main administrator account. Claiming otherwise reveals dishonesty or ignorance and incompetence. This approach isn't common among professional applications when software must run without requiring system-wide administrative changes. Claiming so reveals dishonesty or ignorance and incompetence. I've installed many professional applications as a CompTIA- and Microsoft-certified System Administrator and I've never seen this approach in 15+ years. Any properly-developed software installed to the standard Program Files folder can run without requiring system-wide administrative privileges. It does negatively affect the actual service and its usability: only the main administrator can use it. Claiming otherwise reveals dishonesty or ignorance and incompetence. No corporate nor team-based customer can successfully deploy nor use this software in a professional business environment unless their users use the main administrator account, which is dangerous, bad practice, and against Microsoft guidelines and common sense. We are a corporate and team-based customer and we couldn't successfully deploy nor use the software in our professional environment at all even after granting the user administrator privileges, which indicates that the described behavior does prevent normal business use. Which it obviously does, because no proper corporation or team-based customer has a professional environment where standard users use the main administrator account. One of our users managed to install it at home and still couldn't properly use it. We gave up.
Update (03/13/2026): Tried iRender GPU. Works fine. It also installed in the user profile folder of the main administrator, but only because that's the user we used to install it. Unlike RebusDrop, it installed and ran correctly in the user profile folder of the signed-in user after granting the signed-in user administrator privileges and continued running correctly after removing the administrator privileges.
Reply from RebusFarm
Hi Felipe,
The point raised concerns internal software design and installation methodology, not the functionality, performance, or reliability of the service itself. The installation path is a deliberate technical choice to ensure compatibility, correct permissions handling, and stable operation across a wide range of Windows environments.
This approach is common among professional applications, particularly when software must run without requiring system-wide administrative changes. It does not negatively affect the actual service or its usability.
We also support many corporate and team-based customers who successfully deploy and use the software in professional environments without issues, which indicates that the described behavior does not prevent normal business use.
As such, this concern relates to implementation preferences rather than a defect in the render service.
