Whenever you attempt to move a module to another page the request is ignored.  There have been a number of posts explaining it could be down to a core framework bug, but the most common reason is very simple once you track down the cause!

This is a common mistake in a number of third party and even core modules!  The only modules that show this behaviour utilize a settings page that Inherits ModuleSettingsBase.

The reason the module will not move is because of the following code:

Public Overrides Sub UpdateSettings()

    Try

    'Your update code....

    'Code causing problem....
    Response.Redirect(NavigateURL())

    End Try
        Catch exc As Exception
    End Try

End Sub

Removing the Redirect code allows the parent Module Settings page to handle the redirect, suddenly the module starts to behave as it should!