I have created a backup image of windows 10 via macrium reflect..
Now I need find out what version of windows is the image.
So does it store windows version number in a file I can open to view?
I can mount the image and can browse the files in that image.
I don't think there is a file stores Windows version number but you can take look at "C:\Windows\Logs\DISM\dism.log" file.
Never tried that before but doesn't Macrium reflect have a Viboot (Virtual boot)
If so you might be able to run Winver.exe within it to get version.
Be careful about using the dism.log file. I haven't found it to be accurate.
Perhaps use Nir Sofer's OfflineRegistryView on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ of the mounted image?
The ReleaseID entry holds the 'version' value, the CurrentBuild entry holds the 'build' value whilst the UBR entry holds the 'release' value.
Hope this helps...
Look for the ntoskrnl.exe file and check it's version number.
Usually in C:\Windows\System32
Right click on it, select "Properties", then select the "Details" tab
It's formatted as 10.0.17763.615 (your version may be different)
And there is a file that stores the Edition [Home/Pro]. See Windows 10 home or pro - TenForums
Denis
I've now posted a method for getting the Edition, Version, Build from a Windows disk [even a non-booting one] or a system image in
Get Edition, Version, Build of a non-booting computer - TenForums
Denis
In addition, ShowKeyPlus can retrieve the edition, version and key from an offline system. This is from a mounted MR image....
Bree,
Yes. The OP in that thread had asked for a solution that could be done while booted into a Windows 10 installation disk's command prompt so I mentioned jdc1's method [above] in my first response in that thread [post #3] then went on to describe [post #6] retrieving the target disk's Software hive for analysis on another computer to avoid the ambiguity caused by Versions 1903, 1909 sharing the same kernel version. It is that post #6 that the link points to.
While I've got your attention, am I right in thinking that you play around with VMs a lot? If so, do you happen to have a VM of a x86 Windows 10 running on a x64 CPU? I seem to have made a complete horlicks of my records from last year and cannot make out what results I got for a couple of Registry entries.
- I wanted to know two Registry entries in this VM but my notes were written up so badly that I cannot tell which were from which test and I've since removed VirtualBox so I'd have to start again from scratch.
- One SubKey is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
- The other one is HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0
- I know what the .Reg export of a x64 OS on a x64 CPU entry looks like.
- I know what the .Reg export of a x86 OS on a x86 CPU entry looks like.
- I do not know what the .Reg export of a x86 OS on a x64 CPU entry looks like. I have either mis-filed or mis-labelled those results.
- The point of the test was to try to identify a parameter that would identify the presence of a x64 CPU even if x86 Windows has been installed on it.
- The OP in that other thread had not asked about this particular test but I would have added it if I had been certain of my facts.
I've just been turning my place upside down failing to find my spare SATA disk on which I could simply install a x86 OS in a x64 computer without disrupting my operational computers for too long.
Denis
Quote
