
Game Overview
A lonely country house becomes a pressure cooker for paranoia in this first-person psychological horror story. Noam Elfer has barely settled into his new home when the knocking begins, turning an ordinary night into a drawn-out confrontation with death, guilt, and unstable memories. Every visitor at the front door carries a connection to the house’s grim history, and the tension comes less from outright action than from the fear of deciding what should be let inside. The mood is intimate, oppressive, and deliberately unsettling, built around the sense that Noam cannot fully trust what he sees or remembers.
Players move through the house, investigate its rooms, and answer the recurring knocks that punctuate the night. Each encounter reveals another fragment of a dead character’s life, gradually linking their personal tragedies to Noam’s own nightmare. The central loop revolves around environmental exploration, story discovery, and enduring escalating supernatural disturbances rather than fighting monsters with weapons. Expect a focused, narrative-led experience where observation matters: clues in the home, changes in familiar spaces, and the details behind each visitor help piece together what is real, what belongs to the past, and why Noam is caught in the middle.
Who Knocks stands out by making the front door a source of dread rather than safety; every knock signals a new story and a potential shift in the protagonist’s fractured reality. Its horror leans toward anxiety, disturbing imagery, and emotional revelations instead of combat-heavy chases, giving it a more personal feel than a typical haunted-house scarefest. The interconnected cast gives the narrative structure beyond simple jump scares, as each ghostly presence contributes to the larger picture of Noam’s condition. Fans of compact first-person horrors such as Layers of Fear, Visage, or P.T.-style hallway nightmares should find plenty to appreciate, especially if they prefer atmosphere and psychological unease over action.
Screenshots
Installation
- Select the Download button at the top of this page to open UploadHaven.
- On UploadHaven, wait for any countdown, then select Free Download. Optional: UploadHaven Pro for faster downloads.
- When complete, extract the archive to a Who Knocks folder using 7-Zip.
- Open the extracted folder and start the game normally.
- For errors, check Setup Guide & Troubleshooting below. Keep your security software enabled.
System Requirements
- OS: WINDOWS® 7, 8, 8.1, 10, 11
- Processor: Intel® Core™ i3 or AMD Ryzen™ 3
- Memory: 6 MB RAM
- Graphics: NVIDIA® GeForce® GTX 950 or AMD Radeon™ R7 370
- DirectX: Version 10
- Storage: 10 GB available space
Setup Guide & Troubleshooting
How do I fix missing DLL errors for Who Knocks?
After extracting Who Knocks, navigate to the _Redist or _CommonRedist folder inside the game directory and install DirectX, Vcredist, and any other dependencies included.
What should I do if the downloaded file is corrupted?
The full archive is 2.36 GB — make sure your download completed fully before extracting. Use 7-Zip to extract the files. If you still see a "file corrupted" error, re-download and try again.
Do I need to run the game as administrator?
Usually, no. Start the game normally from the extracted folder. If you see a permissions or save error, check that the folder is writable and follow the game's documented fix. Only grant administrator access when a trusted game's specific setup requires it.
How do I update my GPU drivers for this game?
The game won't launch — what should I try?
Check that extraction completed and your PC meets the system requirements, including Version 10. Note any error message before choosing a fix. If it identifies a missing runtime, install the required DirectX components or Microsoft Visual C++ Redistributable from Microsoft.
My antivirus is blocking the game — is it safe?
A warning needs to be investigated; the download source alone cannot confirm that a file is safe. Keep your security software enabled and review the detection details. Do not run or restore a flagged file unless you have verified that it is a false positive. If you are unsure, leave it quarantined.