Talk:MagicJack/Support Resources/How-To/Completely Remove MJ

As of this time of writing, there seems to be an error in the article text, where taking ownership and full control seem to be equated - they're not the same, and both are necessary. I wrote the following section; a couple of minutes later the entire article was replaced by short Spanish text on the conquest of Greece by Rome(?!) I have replaced the original text with my addition, but include my addition here in case anyone finds it useful, or decides to re-add it.

P.S.: getting control of file system and registry objects
Added comment by Wikipedia registered user pol098, reachable there

Re the paragraph ''Delete them. If the Registry won't allow you to delete them, you may need to change Ownership by right clicking on the key, selecting Permissions, Advanced and checking "Full Control"''. I don't want to edit the paragraph as my experience is not with MagicJack, but (particularly in Windows 10) I've found that to solve some permissions problems with files/directories and with registry keys it is necessary both (logged in as an administrator user) to Take Ownership and to take Full Control; these are separate actions. I find that, as an administrator user, I have to do both; even taking ownership by my account, and then giving Full Control to Administrators doesn't work, it has to be a named administrator user account. If you can make things work without all this, so much the better; but this procedure may work where omitting some steps doesn't.

In some particularly recalcitrant cases I've found an elevated command prompt is the only thing that works (Win10: right-click start button, Command prompt Admin). I had a directory structure I couldn't delete with the above ownership/control method; I ultimately opened an elevated prompt and used commands MS-DOSsers will know: chdir or cd; rmdir or rd; dir; del. After changing ownership/permission in Explorer (I did this separately for the top level directory, its subdirectory, and the single file in the subdirectory) but still unable to delete, I had to navigate down two levels, delete the file, up one level, remove the subdirectory, up another level, finally delete the top directory. Perhaps I'd have had less work with inherited permissions; perhaps I could have used DELTREE or something similar from the top level, but it worked and I didn't investigate further. If you have a lot of deletions to make, it's been suggested that you create a new administrator user, grant Full Control of the entire registry tree (I think ownership would be dangerous), make the deletions, then remove the temporary user.

HTH

Best wishes, 213.208.107.91 (discuss) 20:43, 21 July 2016 (UTC)