Dont open developer tools как исправить

I’ve been trying to get a video source from a web site but when I open the dev tools to do so, It shows me this message: “Dont open Developer Tools”.

So far I have tried:

  • Turn off javascript ->doesn’t work, doesn’t load the video.

  • Find the function:

olplayer.src({type:"application/x-mpegURL",src:"https://127.0.0.1/no_video.mp4.m3u8"});
document.body.innerHTML="";
document.write(" Dont open Developer Tools. ");
throw new Error(" Dont open Developer Tools. ");
self.location.replace('https:'+window.location.href.substring(window.location.protocol.length));

set a breakpoint and reload, run:

Object.defineProperty(window, "console", {configurable: false});

Any ideas how to bypass this protection?

Chumpocomon's user avatar

Chumpocomon

6611 gold badge6 silver badges12 bronze badges

asked Dec 14, 2019 at 19:29

Unnamed10110's user avatar

1

You are probably talking about a video hosted on hqq.tv. Their code uses a check() function which does all the nasty magic to block all hacking attempts, so the easiest way to bypass the protection altogether is to disable this function.

Since recently, Chrome supports local overrides for javascript code (I found out about this from this SO thread). A bit nicer explanation on how this works can be found on Medium.

So I went ahead and located the check() function (in my case it was hqq.tv/js/embed.129.js) and added it to Overrides. In the overridden version I found the check() function and added return true; to its beginning:

function check(){return true; var element=new Image(); ...

However, this only disables the Dev Tool protection, but doesn’t make your life much easier in terms of saving the video. My own solution doesn’t work on hqq.tv, nor had I any luck with the solution suggested on videohelp forum. However, I was able to capture the stream using Stream Recorder Chrome extension.

Dharman's user avatar

Dharman

30.3k22 gold badges84 silver badges132 bronze badges

answered Feb 14, 2021 at 11:25

Vlad Nikiforov's user avatar

Vlad NikiforovVlad Nikiforov

5,8221 gold badge12 silver badges18 bronze badges

I Found a bypass for the detection, use FireBug Lite extension for chrome (or the browser u prefer). It bypasses the detection because it is an extension

answered Jun 22, 2022 at 13:51

Jesse de gans's user avatar

3

After upgrade to Windows 10, I can’t get the F12 Developer Tools to show / work under MS Edge.

IE 11 developer tools do still work, but I can see rendering differences on my websites I am working on between them, so could do with getting them working under Edge.

I am presuming they are available??

Have already tried the re-register packages fix, as well as reset Internet Options, but nothing works.

asked Sep 10, 2015 at 11:30

Glenn Walker's user avatar

The following issue page contains a solution for this in the comments, which worked for me:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/18153935/

If you are allowed to use powershell, execute the following command as your user to fix the dev tool: Add-AppxPackage -register "C:windowsSystemAppsMicrosoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbweAppxManifest.xml" -DisableDevelopmentMode -Confirm:$false

answered Aug 7, 2018 at 11:00

Thomas's user avatar

ThomasThomas

1841 silver badge5 bronze badges

0

I work on the Microsoft Edge team, and have not personally heard of any issues regarding the developer tools not working. As pointed out in another answer here, the tools will only be available via menu and F12 when you navigate to a document. The tools don’t work for things like the New Tab Page.

If you continue to experience issues with the Developer Tools, please share additional information about your build of Windows 10 (run winver from Run), and Microsoft Edge (version number available in Settings). I’ll gladly file an issue for further investigation.

In the meantime, you could try another utility on Windows 10 called the F12 Chooser. You’ll find this under C:WindowsSystem32F12F12Chooser.exe. This will identify all possible debug targets presently opened on your machine. You should see an instance of Edge enumerated.

Community's user avatar

answered Sep 10, 2015 at 21:43

Sampson's user avatar

SampsonSampson

264k74 gold badges538 silver badges561 bronze badges

9

Answer

If you open Edge without having gone to a website first, then the F12 Developer Tools will not be available. For instance, if you just open a new tab, then you will not have the tools. Once you actually go to a website, the tools will again be enabled.

Disabled

Disabled in a new tab.

Enabled

Enabled at a website

answered Sep 10, 2015 at 20:59

Shaun Luttin's user avatar

Shaun LuttinShaun Luttin

131k79 gold badges398 silver badges464 bronze badges

0

The “developer tools blank” phenomenon is a known issue, as you can see here: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/15458103/

The solution is yet unknown. I have the same effect here on my computer with one account, but I can see the tools page with a different user account on the same machine. So I think this might be an issue connected to the user profile.

answered Jul 26, 2018 at 8:13

Birgit Nietsch's user avatar

1

I don’t know if this will help anyone. But I use edge a lot and after one update my F12 didn’t work, I searched and found out that the update turned off the F12 on edge settings. Open the Settings find for F12 and mine was disabled.
That simple, and never thought about it.

answered Jan 28 at 15:50

Tiago Camacho's user avatar

Absolutely nothing worked for me, except this:

Using Administrator permissions, delete the following files and restart Developer Tools:

The folder is %windir%SystemAppsMicrosoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbwemicrosoft.system.package.metadataAutogen and the exact file depends on system arch:

  • x64: JSByteCodeCache_64
  • x86: JSByteCodeCache_32

answered May 8, 2019 at 8:45

Álvaro González's user avatar

Álvaro GonzálezÁlvaro González

141k40 gold badges257 silver badges356 bronze badges

2

I have this problem today!

I debugged yesterday, no problem, then ran the latest big microsoft update last night and today I have this problem.

You have to close the tab and reopen it and then everything is ok!

Bhargav Rao's user avatar

Bhargav Rao

49.4k28 gold badges121 silver badges140 bronze badges

answered Apr 30, 2020 at 19:07

David Lipschitz's user avatar

2

After upgrade to Windows 10, I can’t get the F12 Developer Tools to show / work under MS Edge.

IE 11 developer tools do still work, but I can see rendering differences on my websites I am working on between them, so could do with getting them working under Edge.

I am presuming they are available??

Have already tried the re-register packages fix, as well as reset Internet Options, but nothing works.

asked Sep 10, 2015 at 11:30

Glenn Walker's user avatar

The following issue page contains a solution for this in the comments, which worked for me:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/18153935/

If you are allowed to use powershell, execute the following command as your user to fix the dev tool: Add-AppxPackage -register "C:windowsSystemAppsMicrosoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbweAppxManifest.xml" -DisableDevelopmentMode -Confirm:$false

answered Aug 7, 2018 at 11:00

Thomas's user avatar

ThomasThomas

1841 silver badge5 bronze badges

0

I work on the Microsoft Edge team, and have not personally heard of any issues regarding the developer tools not working. As pointed out in another answer here, the tools will only be available via menu and F12 when you navigate to a document. The tools don’t work for things like the New Tab Page.

If you continue to experience issues with the Developer Tools, please share additional information about your build of Windows 10 (run winver from Run), and Microsoft Edge (version number available in Settings). I’ll gladly file an issue for further investigation.

In the meantime, you could try another utility on Windows 10 called the F12 Chooser. You’ll find this under C:WindowsSystem32F12F12Chooser.exe. This will identify all possible debug targets presently opened on your machine. You should see an instance of Edge enumerated.

Community's user avatar

answered Sep 10, 2015 at 21:43

Sampson's user avatar

SampsonSampson

264k74 gold badges538 silver badges561 bronze badges

9

Answer

If you open Edge without having gone to a website first, then the F12 Developer Tools will not be available. For instance, if you just open a new tab, then you will not have the tools. Once you actually go to a website, the tools will again be enabled.

Disabled

Disabled in a new tab.

Enabled

Enabled at a website

answered Sep 10, 2015 at 20:59

Shaun Luttin's user avatar

Shaun LuttinShaun Luttin

131k79 gold badges398 silver badges464 bronze badges

0

The “developer tools blank” phenomenon is a known issue, as you can see here: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/15458103/

The solution is yet unknown. I have the same effect here on my computer with one account, but I can see the tools page with a different user account on the same machine. So I think this might be an issue connected to the user profile.

answered Jul 26, 2018 at 8:13

Birgit Nietsch's user avatar

1

I don’t know if this will help anyone. But I use edge a lot and after one update my F12 didn’t work, I searched and found out that the update turned off the F12 on edge settings. Open the Settings find for F12 and mine was disabled.
That simple, and never thought about it.

answered Jan 28 at 15:50

Tiago Camacho's user avatar

Absolutely nothing worked for me, except this:

Using Administrator permissions, delete the following files and restart Developer Tools:

The folder is %windir%SystemAppsMicrosoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbwemicrosoft.system.package.metadataAutogen and the exact file depends on system arch:

  • x64: JSByteCodeCache_64
  • x86: JSByteCodeCache_32

answered May 8, 2019 at 8:45

Álvaro González's user avatar

Álvaro GonzálezÁlvaro González

141k40 gold badges257 silver badges356 bronze badges

2

I have this problem today!

I debugged yesterday, no problem, then ran the latest big microsoft update last night and today I have this problem.

You have to close the tab and reopen it and then everything is ok!

Bhargav Rao's user avatar

Bhargav Rao

49.4k28 gold badges121 silver badges140 bronze badges

answered Apr 30, 2020 at 19:07

David Lipschitz's user avatar

2

Вероятно, вы говорите о видео, размещенном на hqq.tv. В их коде используется функция, которая блокирует все попытки взлома, поэтому самый простой способ полностью обойти защиту — отключить эту функцию.

С недавнего времени Chrome поддерживает локальные переопределения для кода javascript (об этом я узнал из этой темы SO ). Немного более приятное объяснение того, как это работает, можно найти на Medium.

Поэтому я пошел дальше и нашел функцию (в моем случае это была
hqq.tv/js/embed.129.js) и добавил его в Overrides. В переопределенной версии я нашел
check()функцию и добавил
return true;к его началу:

      function check(){return true; var element=new Image(); ...

Однако это только отключает защиту Dev Tool, но не сильно упрощает вашу жизнь с точки зрения сохранения видео. Мое собственное решение не работает на hqq.tv, и мне не повезло с решением, предложенным на форуме videohelp . Однако мне удалось захватить поток с помощью расширения Stream Recorder для Chrome.

Recently I had to replace my Windows PC at work, and as a result, had to reinstall all of my applications, including Google Chrome. When I tried to open Chrome Developer Tools using the F12 key, nothing happened. The Inspect option seen when right-clicking on a web page was grayed out. I opened the drop-down menu to try to open DevTools from there, and that option was also grayed out.

Developer Tools is disabled

Several searches indicated that one could look at Chrome Policies (accessible at chrome://policy if you’re running Chrome) to see if it was disabled there. Sure enough, that was the case.

Chrome policy page showing DevTools disabled

Chrome Policies are not editable from this page; in Windows one must edit them via the Windows Registry.

Open the Registry using regedit.exe from a Command Prompt or a shortcut in the Start Menu, and navigate to [HKEY_LOCAL_MACHINESOFTWAREPoliciesGoogleChrome] and set the key called DeveloperToolsDisabled to 0.

Registry Editor showing [HKEY_LOCAL_MACHINESOFTWAREPoliciesGoogleChrome] branch

Close the Registry Editor, go back to the Chrome Policies tab, and click the Reload button in the upper left-hand portion of the screen.

The “true” value for the DeveloperToolsDisabled Policy Name should change to “false”.

Now you should be able to open DevTools again!

Добавить комментарий