A bypass of DyKnow, powered primarily by the Windows win32 API.
DieKnow will significantly improve device performance by lowering CPU utilization that is being used by DyKnow. On my organization HP computer with a 12th Generation Intel Core i3 1210U, this runs at less than 1% CPU. This CPU has a Cinebench R23 score of 823 pts.
For ease of use, a beta GUI application is located in gui.pyw, built entirely by the Windows API without an external library such as Qt or GTK.
The two main principles of design I have used are:
- Performance, a large side effect of DyKnow.
- Comprehensiveness
Caution
Disclaimer: Do not use DieKnow to cheat. Cheating and directly immoral or dishonest usage is not condoned here in any way.
| Download now |
Save with Ctrl+S and double-click the downloaded file to run.
Tutorial.mp4
- 6 MB of free RAM
- 7 MB of free storage
- x86 Intel or AMD processor
- Windows 10 or 11 OS
Other operating systems besides Windows will not be supported because of lack of usage and because DieKnow is strongly tied to the platform-speciifc win32 API. ARM will not be supported because of the lack of usage and because I will not be able to test it.
Starting with DieKnow 2.6, DLLs are dynamically linked. Therefore, an Internet connection is required to download required DLL binaries on the first run. These binaries are comprised of the MSVC C/C++ Redistributable Runtime and the compiled DieKnow module. Some DLLs are assumed to be on the system and they are not downloaded.
| DieKnow Shell | DieKnow GUI |
 |
 |
Compilation instructions can be found here.
About DieKnow:
- This DOES NOT need administrator privileges, just a Python installation, which is often found in the Software Center.
- DOES NOT need a C++ compiler.
- DOES NOT need to run an executable or a batch file, which is usually blocked by the school via Windows AppLocker.
- DOES NOT have any external dependencies, besides the C++ standard library and the Windows API, which are preinstalled.
- Written in high-performance C++ code for maximum performance, faster than many other alternatives you can find open-source.
What can DyKnow do:
- Monitor your device screen (including when you press "Show password" when typing a password)
- Monitor your search history
- Monitor what apps you've been on
- Lock your device
- Track your device's location
- Make your computer really, really slow
- Track your keystrokes
- Make your computer useless
When it is running, you'll see the DyKnow icon disappear from your taskbar. 💀
If you want to allow DyKnow to start up once the computer is logged on, you can perform the following steps:
- Create a shortcut to the
main.pyorgui.pywfile, depending if you want to start up with a GUI or a console. - Cut the shortcut by pressing
Ctrl-X. - Press
Windows-Rto open up the Run window. - Type
shell:startupin the input box that appears. - In the Windows Explorer dialog that appears, paste the shortcut you copied in step 2.
That's it! It may take around two minutes for it to start up.
Start the DieKnow process. DyKnow executables will be terminated forcefully every 50 milliseconds, or whatever is set as the interval option in settings.conf, which is sufficient to keep DyKnow consistently closed down. If the delay was too low (or none at all), CPU usage would increase. On an Intel Core i3 CPU, an interval of 50 milliseconds can be handled at less than 1% CPU.
Kill the DieKnow threads but keep the app running. Threads associated with DieKnow will be terminated.
Retrieve the number of executables killed by DieKnow.
Retrieve the files in the DyKnow installation directory.
It should return something similar to this.
Files in C:/Program Files/DyKnow/Cloud/7.10.22.9:
amjbk.exe
Demo32_64.exe
Demo64_32.exe
dkInteractive.exe
DyKnowLogSender.exe
DyKnowTest.exe
kyplu.exe
MonitorStateReader.exe
winProcess.exe
Here, kyplu.exe and amjbk.exe are the main DyKnow monitoring executable, but as the name is changed randomly each time it’s restarted, it will vary.
Exit the DieKnow application and destroy all threads associated with it.
DieKnow provides an Python API that is accessible at dieknow.py, which just calls the C++ functions. The C/C++ API is found in the src directory.
Directory structure:
src- Python and C++ source filesdlls- precompiled C++ source files as shared objects. It's advised not to mess around with these files.dieknow.dll- compiled DieKnow C/C++ API nad runtime
api.cpp- DieKnow functions and C++ APIgui.cpp- GUI applicationsystem.cpp- system interaction and processingsettings.cpp- settings loader for DieKnowdieknow.py- DieKnow Python APImain.py- Shell-like interface to DieKnow APIgui.pyw- Python link to C++ GUI
tests- nonstatic build testingtestdll.py- Dependency checker for DLLs
Associated *.h files in the src directory are the includes for the implementation found in *.cpp.
Most users' devices, such as Intel Pentium Silver, N-series and Core i3, do not have a lot of computing power and are more focused on lower power draw rather than performance. As DieKnow is intended to be run constantly in the background, it is especially important this has low resource usage so it has no effect on running programs.
See the compiling guide. You will need a C++17 or higher compiler. GitHub Actions automatically builds binaries for every push.
Warning
A current bug with DyKnow sometimes may occur where DyKnow executables that are supposed to be deleted are not deleted, and over time while this app is running the DyKnow installation folder will increase in size by approximately 10 KB/s. In this case, just restart your device and wait for DyKnow to start back up before you kill it, and the excess executables will be cleared. This is very rare and has only been reported once.