Hi, Is there any tool or method that would allow the editing of my Windows version? Let's say I'm on build 14393.98, is there any way to change it to 14393.105? It's not a cosmetic change that I'm looking for, but an actual spoof of the Windows version. Thanks
Off Offcourse you can do do that , The bigger question is why? Just imagine what happens when you update your windows....
How would I go about doing it then? Reason being, when updating, I may acquire some undesired changes to my system and would still like to use apps that require the very latest hotfix.
The so called "Windows version" showing in winver is just a registry value that Microsoft put for propaganda and the CU only update individual files/components the OS build version will be always 14393.0
accretio: Revision (UBR) is propaganda. Curent build labs is 14393.103.amd64fre.rs1_release_inmarket.160819-1924
Maybe Resource Editors to modify winver.exe or explorer.exe ntoskrnl.exe etc.. Resource Editors can change all kinds of "resources" inside win32/64 binaries witch will likely get fixed by a sfc.exe. depends on what app you want to trick checks for and where it checks? windows updates im sure checks several places. sounds like a part recipe for a frankin build of windows and more pita than its worth. You can also find/change the build version in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" but I cant imagine what might happen if you do. ~MC
Pretty much. I basically want to cheat the Store, which often requires having the latest update upon app releases. Guess I should've been clearer. Please see above. More like fool the Windows Store. But fooling both would be a bonus lol.
Awesome. I kinda figured as much, but wasn't really sure. Looks like my work is cut out for me then. I see. You have both been really helpful. I know it's a bit much to ask, but have you guys any idea as to which file(s) I would need to change to fool the Windows Store? For now, I will follow MrChris's suggestion and go try out resource editors. I have tried editing the values in CurrentVersion but to no avail Really appreciate the help so far, this forum is awesome.
There are many ways of determining version information. Documented APIs, information in the registry, presence of CU packages, version info resources of ntoskrnl or ntdll, or other system files, etc. It would be very difficult to properly spoof all of those. Pretty sure the Store isn't going to use information in the resources to determine version. Besides, editing ntoskrnl.exe will invalidate its signature and winload will refuse to boot it. The "cleanest" way to fool a specific program would be to determine how it obtains the version information, and then inject code to modify how it does it (e.g. hook version info APIs). But of course, the required OS version may also be checked by the appx installer, or by the runtime when trying to start the app, or by the app itself...
Making changes to those important system files won't be a good idea. Possibly, it will harm the operation of the Windows 10 all together.
Your post has been extremely helpful. You're most likely right about the resource information, so I'll likely need to do some dll injection or bypass the the sandbox all together. I doubt the appx installer has that kind of security and my current plan is simply to bypass the Windows Store's update thing for now. I'm running a VM just in case.
Any tool exists to hook well known APIs about Windows version, build number, build string, family, service pack level, ....? A first step would be to list these values in one place, according to each source. - Registry - ntoskernel.exe - Kernel32.dll - ...