Windows 10 activation

I'm using an iso generated from the MCT tool. Should I be getting my iso from somewhere/something else? I remember seeing on the MCT page it said pro/home were all in one so I'm assuming the pro install is there

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Your solution? I believe i mentioned that deleting all other indices als would work: https://forums.mydigitallife.net/threads/windows-10-activation.76197/page-4#post-1409064

 

humm, that's true so let's say that i thought about it before you post it here

 

Code:

MRP - OEM Query Tool v17.0 Enhanced  -- 2:38pm Mon 02/05/2018

Basic OEM Information For This Computer
---------------------------------------
 OS Name:                 - Windows 7 Professional
 OS Architecture:         - x64
 OS Edition {Registry}:   - Professional
 OS Real Edition {WMIC}:  - Professional
 OS Language Name/Code:   - en-US ( 1033 [409h] )
 OS Locale:               - en-US
 OS Language Value:       - ENU
 Processor Name/Type:     - Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
 Processor Description:   - Intel64 Family 6 Model 142 Stepping 10
 Processor Architecture:  - 32/64 Bit Instruction Set
 Processor Cores/Threads: - [4] / [8]
 HDD Mode/Partition type: - [Undefined, possible customized chipset.] / [MBR]
 Bios Version:            - [1.0.4, 09/08/2017]
 Total Physical Memory:   - [7845 Mb]
 Available Memory:        - [6891 Mb]

Scanned DMI
-----------
 #1 CSProduct Name:       - Inspiron 5570
 #2 CSModel Name:         - Inspiron 5570
 #3 CSBaseboard Prod:     - 09YTN7
 #4 CSProduct Vendor:     - Dell Inc.
 #5 CSManufacturer:       - Dell Inc.
 #6 Baseboard MFR:        - Dell Inc.
 #7 Serial/Service Tag:   - Not Shown On Saved Report.
 #8 BIOS ID:              - DELL
 #9 SLIC OA:              - 2.1
#10 Installed PID Key:    - Key Not Shown On Saved Report.
#11 MSDM Key [OEM-DM]:    - Not Shown On Saved Report.
#11 MSDM Edition Info:    - Win 10 Core MSDM
#12 BIOS Mode:            - Legacy
#13 Certificate:          - Present
#14 License Status:       - Licensed

Summary
-------
 OEM Theme/Branding:      - Dell [id: #4]
 OEM Activation Vista/7:  - Dell [id: #8]
 Valid OEM OS:            - Vista/Win7/Win8.x/Win10 Only

Well, it looks like my QT is quite old (17 vs 48!)

Glad to see my non-results are being repeated. So if I use the included PID.txt will it upgrade/activate the install to win 10 pro if it is coming from win 7 sp1 pro?

 

No it won't work as @Enthousiast has already tested it without success so why don't you just use gimagex tool to make this work as i've already mentionned it in my previous posts.

 

Wow QTv17 must be april-june 2017 when that was out

Seems the PID.txt causes a hang - it does on a Virtual Machine...

 

Yes, that's an old QT, but it shows the correct info about the MSDM

I am giving @mxman2k's PID.TXT option one other run, will report asap.

If you want you can export the pro index from the "usb:\sources\install.wim" to a new install.wim and replace the existing one:

Code:

dism /Export-Image /SourceImageFile:"x:\install.wim" /SourceIndex:y /DestinationImageFile:"z:\install.wim" /Compress:max /checkintegrity

Depending on what ISO you have, y is the index nr for Pro.
On 16299.xxx iso it will be: on en-US it's index 6.

 

I just tried adding hte PID file. It offered me Pro and only pro. Doing the upgrade now. will report back in once it is done to see if it stayed activated or not

 

Yup sounds about right. I dont get around to updating mine all that often (as you can see lol)

 

really ? good to hear but how come it worked for you when it didn't for @Enthousiast ?

 

You need to login to view this posts content.

 

Big for @mxman2k , thank you for this great trick my friend, you are the man

 

Its only because i done a LOT of research when working on the MRP/QT , what does what and when it not, why not etc then find a work-a-round

 

Up till now the ei.cfg from mrp was sufficient but something seems to have changed.