These days i am really lazy and hate typing so...
First, this is no hiding tools or w/e fancy name you choose tomorrow. It just moves you history files which is totally a waste of time since a forensic analysis 101 student will flag that chrome tool folder the moment they open the chrome dir and then why the waste of time.
If i was writting a tool to look for the history files, i would have afew lists of%appdata% know directories for the browsers and recursively look into each folder for filenames , file formats [magic number here], blah blah. Bottom line, this was prolly good learning project but get to better useful things. If i have the time to fucking hide and unhide the history i am soo lame it would have been easier to just delete it on every successfull shutdown. {tool idea number one]
Or better it would have been easier to write a tool that deletes most of the browser artifacts for security reasons [tool idea number #2]. My man El Chapo got fuck due to Chrome incognito mode fucking up and leaving artifacts, so maybe if El Chapo had this tool, he would not be in jail.
Another thing, i don't care how the code on your machine looks like, but if it doesn't work in this project, delete it and have no fear, stackoverflow will be around to give you that solution tomorrow. What i mean is that when shring code, take caution to delete that commented out code, first it looks ugly then you run a risk of commenting out a password and revealing it to the whole public.
Commandline menus, fuck TUIs when you all suck at them. If you are not going to do a GUI, since you javafags like them, get commandline arguments from the user the right way than these sophomore codeways.
tr;ld, READ UP.