- Joined
- Feb 27, 2010
- Messages
- 695
- Reaction score
- 335
- Trophies
- 1
- Age
- 34
- Location
- Taipei, Taiwan
- XP
- 1,320
- Country

I noticed your Hybrid Analysis in-depth results showed the installer would "reboot the computer".
Maybe it's just me, but I don't recall devkitPro requesting to reboot computer once installed.
But if it did, then it's for setting up the environment variables to point $DEVKITPRO and $DEVKITARM to the correct installation paths, in order for Makefiles to work. And it may be the cause for virus scanners to flag it as suspicious, which is frankly a false positive.
Completely harmless.
I'm not sure what or why other parts are flagged as suspicious for, so maybe others have better insights on why a normal installation procedure gets flagged as suspicious, and it's really not?
Maybe it's just me, but I don't recall devkitPro requesting to reboot computer once installed.
But if it did, then it's for setting up the environment variables to point $DEVKITPRO and $DEVKITARM to the correct installation paths, in order for Makefiles to work. And it may be the cause for virus scanners to flag it as suspicious, which is frankly a false positive.
Completely harmless.
I'm not sure what or why other parts are flagged as suspicious for, so maybe others have better insights on why a normal installation procedure gets flagged as suspicious, and it's really not?
Last edited by delete12345,






