This usually happens when you have an add blocker, antivirus, or similar program that prevents communication between the inspector and the chrome instance.
For me, the problem was the download manager program, which was supposed to capture downloads from the browser, as soon as I killed it, the inspector worked fine
source share