diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..267c90f
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,22 @@
+# Contributing guidelines
+
+**English** | [русский](CONTRIBUTING.ru-RU.md) | [Français](CONTRIBUTING.fr-FR.md) | [Deutsch](CONTRIBUTING.de-DE.md) | [Magyar](CONTRIBUTING.de-HU.md)
+
+## Reporting an issue [![](https://isitmaintained.com/badge/resolution/zeffy/wufuc.svg)](https://isitmaintained.com/project/zeffy/wufuc)
+
+#### Before you create an issue, please make sure of the following:
+
+- Are you using at least the [latest stable version](../../releases/latest)?
+- Have you tried restarting your computer?
+
+#### After you've confirmed those things, please create an issue and include the following information:
+
+- Navigate to where you installed wufuc, and attach all the `*.log` files to your issue.
+- What build are you using? Stable release or unstable AppVeyor builds?
+- What is the file version and/or SHA-1 hash of `C:\Windows\System32\wuaueng.dll`?
+- Any other information you feel is relevant to your issue.
+
+## Closure policy
+
+- Issues that don't have the information requested above (when applicable) will be closed immediately and the poster directed to the contributing guidelines.
+- Issues that go a week without a response from original poster are subject to closure at my discretion.
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..e813369
--- /dev/null
+++ b/README.md
@@ -0,0 +1,56 @@
+# wufuc [![](https://ci.appveyor.com/api/projects/status/0s2unkpokttyslf0?svg=true)](https://ci.appveyor.com/project/zeffy/wufuc) [![Click here to tip wufuc on Gratipay!](https://img.shields.io/gratipay/team/wufuc.svg)](https://gratipay.com/wufuc/)
+
+**English** | [русский](README.ru-RU.md) | [Français](README.fr-FR.md) | [Deutsch](README.de-DE.md) | [Magyar](README.hu-HU.md)
+
+[![Click here to lend your support to wufuc and make a donation at pledgie.com !](https://pledgie.com/campaigns/34055.png)](https://pledgie.com/campaigns/34055)
+
+Disables the "Unsupported Hardware" message in Windows Update, and allows you to continue installing updates on Windows 7 and 8.1 systems with Intel Kaby Lake, AMD Ryzen, or other unsupported processors.
+
+## Downloads [![](https://img.shields.io/github/downloads/zeffy/wufuc/total.svg)](../../releases)
+
+### You can get the latest stable version [here](../../releases/latest)!
+
+If you are feeling brave, you can try the latest unstable builds [here](https://ci.appveyor.com/project/zeffy/wufuc). **Use these at your own risk!**
+
+## Sponsors
+
+### [Advanced Installer](http://www.advancedinstaller.com/)
+The installer packages are created with Advanced Installer on an open source license. Advanced Installer's intuitive and friendly user interface allowed me to quickly create a feature complete installer with minimal effort. [Check it out!](http://www.advancedinstaller.com/)
+
+## Reporting an issue [![](https://isitmaintained.com/badge/resolution/zeffy/wufuc.svg)](https://isitmaintained.com/project/zeffy/wufuc)
+
+See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## Preface
+
+The changelog for Windows updates KB4012218 and KB4012219 included the following:
+
+> Enabled detection of processor generation and hardware support when PC tries to scan or download updates through Windows Update.
+
+These updates marked the implementation of a [policy change](https://blogs.windows.com/windowsexperience/2016/01/15/windows-10-embracing-silicon-innovation/) they announced some time ago, where Microsoft stated that they would not be supporting Windows 7 or 8.1 on next-gen Intel, AMD and Qualcomm processors.
+
+It is essentially a big middle finger to anyone who decides to not "upgrade" to the steaming pile of :shit: known as Windows 10, especially considering the extended support periods for Windows 7 and 8.1 won't be ending until January 4, 2020 and January 10, 2023 respectively.
+
+This has even affected people with older Intel and AMD processors! I've received user reports of the [Intel Atom Z530](../../issues/7), [Intel Core i5-M 560](../../issues/23), [Intel Core i5-4300M](../../issues/24), [Intel Atom D525](../../issues/34), [Intel Pentium B940](../../issues/63), [AMD FX-8350](../../issues/32), and [AMD Turion 64 Mobile Technology ML-34](../../issues/80) all being blocked from receiving updates.
+
+## Bad Microsoft!
+
+If you are interested, you can read my original write up on discovering the CPU check [here](../../tree/old-kb4012218-19).
+
+## How it works
+
+Basically, inside a file called `wuaueng.dll` there are two functions: [`IsDeviceServiceable(void)`](https://gist.github.com/zeffy/e5ec266952932bc905eb0cbc6ed72185) and [`IsCPUSupported(void)`](https://gist.github.com/zeffy/1a8f8984d2bec97ae24af63a76278694). `IsDeviceServiceable(void)` is essentially a wrapper around `IsCPUSupported(void)` that caches the result it receives and recycles it on subsequent calls.
+
+My patch takes advantage of this result caching behavior by setting the "first run" value to `FALSE` and the cached result to `TRUE`.
+
+- At system boot the wufuc scheduled task runs as the `NT AUTHORITY\SYSTEM` user.
+- `wufuc` determines what service host group process the Windows Update service runs in (typically `netsvcs`), and injects itself into it.
+- Once injected, it applies a hook to `LoadLibraryEx` that automatically patches `wuaueng.dll` when it is loaded.
+- Any previously loaded `wuaueng.dll` is also patched.
+
+### Several improvements over my batchfile method:
+
+- **No system files are modified!**
+- Heuristic-based patching, which means it will usually keep working even after new updates come out.
+- C is best language!
+- No external dependencies.