You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Fixed offline patcher architecture conflicts
- Now all builds of offline patcher can patch all kernel images
- Previously it was same patcher/kernel due to preprocessor definitions and a bug in code.
- Fixed build errors caused by freestanding memset.
Copy file name to clipboardExpand all lines: README.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,9 +32,14 @@ Getting over it will weaponize this already versatile patch, so disabling PatchG
32
32
- Patch the kernel image itself with offline patcher, instead of runtime patching with driver.
33
33
- This patch can technically be ported to ARM, ARM64 and Itanium hosts but due to lack of an environment to run and debug Windows on these platforms, this is not possible at the moment.
34
34
35
+
## Notes for Offline Patcher
36
+
- Do not use kernel driver with offline patched systems, as the driver is nonfunctional with patched kernels (as there is nothing to remove).
37
+
- Windows XP and earlier builds are not supported, usage of kernel driver is required for those builds.
38
+
35
39
## Notes Per Version
36
40
37
41
### Windows 2000/XP
42
+
- As written above, these builds does not support offline patching.
38
43
-**I KNOW there are "easier" methods, so don't come to say me "muh set GracePeriod to 0" or "muh use TweakNT"**. This tweak for NT 5.x exists more as proof of concept, and both this patch or other tweaks will do the work.
39
44
### Post-reset Windows Vista & Early 7
40
45
- They suck. Avoid using these versions at all. After build expires, buggy WPA breaks the timebomb which makes this patch not get applied anyway, and shows the "Activate Windows" dialog which logs you off if you say no; considering that those builds can successfully finish the windeploy and boot to OOBE/desktop at all in the first place (https://github.com/NevermindExpress/TimeDefuser/issues/3). See https://github.com/NevermindExpress/TimeDefuser/issues/2 and https://github.com/NevermindExpress/TimeDefuser/issues/2#issuecomment-2970226626 for more info.
0 commit comments