Activation problem with W10 AIO ISO

Discussion in 'Windows 10' started by yoda89, Aug 26, 2015.

  1. yoda89

    yoda89 MDL Novice

    Jul 29, 2009
    47
    8
    0
    Hi guys,

    I have a problem with my AIO ISO.
    When I use it to do an upgrade from Windows 7 and Windows 8.x, W10 is NEVER activated after update.

    Of course I'm using the same version (W7 Ultimate 64 to W10 Pro 64 and W8.1 Core 86 to W10 Home 86) and Windows licenses are official.

    I have the error code "0xc004c003" as a lot of people... (Key is blocked).

    Windows Store tells me the license is not official and wants me to buy a new one.

    - slmgr /ato never works.
    - slmgr /dlv indicates "0xc004f034" for "Notification Reason" (which sounds better than "0xc004c003").

    With a DVD created with MediaCreationTool it works.

    Does someone have the same problem (I hope so...) ?

    Thanks :).
     
  2. bromanbro

    bromanbro MDL Member

    Sep 30, 2012
    218
    29
    10
    Are you skipping entering a key? Don't enter the generic key.
     
  3. yoda89

    yoda89 MDL Novice

    Jul 29, 2009
    47
    8
    0
    bromanbro : for sure :).
    fkar : not sure AIO is really supported by M$ :).
     
  4. xinso

    xinso MDL Guru

    Mar 5, 2009
    3,933
    5,282
    120
    #5 xinso, Aug 26, 2015
    Last edited: Aug 26, 2015
    Deleted for misunderstanding.
     
  5. herrkarl

    herrkarl MDL Junior Member

    Aug 3, 2009
    62
    11
    0
    Try this, this what i do if key is blocked:
    - check if windows 7 is activated (slmgr /xpr and slmgr /dlv)
    - use internet explorer to go to microsoft.com/genuine/validate.aspx and validate windows
    - as soon as it says windows is genuine, you can start upgrade to windows 10 (inside windows 7 start setup.exe)
    - do not forget that you need a working internet connection for windows 7 and windows 10 or it will not activate
     
  6. 10aout

    10aout MDL Novice

    Aug 8, 2015
    17
    2
    0
    It happened me once; it was because I disconnected the computer from network while upgrading.

    Doing the upgrade again on the same machine, but keeping it connected, ended successfully.
     
  7. yoda89

    yoda89 MDL Novice

    Jul 29, 2009
    47
    8
    0
    Thanks.

    The computers are connected to network and Windows is genuine.

    When I use the "corepro" ISO from MediaCreationTool it works.

    It's only the AIO ISO which has a problem.... :(.
     
  8. fkar

    fkar MDL Recognized Advisor

    Nov 3, 2012
    1,576
    1,396
    60
    It's already proved that upgrading using ISO will give you permanent activation. As you said, there should be an issue with your AIO.
    And, in many places I read that, AIO's are only for clean install and not for upgrades.!
    But, don't know about yours. :)
     
  9. yoda89

    yoda89 MDL Novice

    Jul 29, 2009
    47
    8
    0
    Yes I've already read too that AIO couldn't not upgrade but I don't understand why it would not...
    It's only with Windows 10 activation because with Windows 8.1 it works.
     
  10. fkar

    fkar MDL Recognized Advisor

    Nov 3, 2012
    1,576
    1,396
    60
    Even 7 & 8.1 AIO's also won't work for upgrades in some scenarios. Don't know what fails :popcorn:
     
  11. yoda89

    yoda89 MDL Novice

    Jul 29, 2009
    47
    8
    0
    Maybe there's a kind of signature somewhere in the WIM file ?

    Did you already try to make a WIM file containing all versions using an existing WIM ?
     
  12. yoda89

    yoda89 MDL Novice

    Jul 29, 2009
    47
    8
    0
    Found !

    We have to delete ei.cfg.
    Windows is clever enough to detect the Windows version to upgrade.

    No problem in boot mode, just choose "ignore" to license key and you can choose which version to install.
     
  13. fkar

    fkar MDL Recognized Advisor

    Nov 3, 2012
    1,576
    1,396
    60
    Okay, noted. Will follow the same in future. :)
     
  14. TGNT

    TGNT MDL Junior Member

    Mar 2, 2010
    96
    3
    0
    That's true. I had problem like that before, but after remove ei.cfg, it activated.