Release Candidate Build 4734.1000 Available On Connect

Discussion in 'Application Software' started by Michelle68, Feb 4, 2010.

  1. olcmania

    olcmania MDL Novice

    Feb 6, 2010
    13
    0
    0
    I also have that update for Microsoft Office 2010 File Validation, but everything still going fine with no problem. :)

    I get that update when i'm still using Public Beta version build 4536. So maybe the update has checked my Office integriy and found out no problem, so when i uninstall it and so some trick with the Office RTM build 4734, it is still going fine. :D
     
  2. kdo2milger

    kdo2milger MDL Senior Member

    Jan 5, 2010
    371
    25
    10
    i just activated mine using solor's script with my tokens.dat and config.ms file along with my mak key edited into the cmd script :) the key that was in the script has already been activated to its limit.
     
  3. aznkid25

    aznkid25 MDL Member

    Aug 20, 2009
    199
    25
    10
    You have to edit the cmd script with your own beta key.
     
  4. stasio

    stasio MDL Expert

    May 3, 2007
    1,193
    1,144
    60
  5. alexcd2k3

    alexcd2k3 MDL Novice

    May 27, 2007
    46
    0
    0
  6. kdo2milger

    kdo2milger MDL Senior Member

    Jan 5, 2010
    371
    25
    10
    #146 kdo2milger, Feb 8, 2010
    Last edited: Feb 8, 2010
    i have the same setup as you.

    it will work.

    you have to uninstall 4734 reboot
    then install beta and save these two files somewhere safe like a folder on the desktop then uninstall beta.

    follow these steps and it should work as it did for me.

    that should get you activated.
     
  7. kdo2milger

    kdo2milger MDL Senior Member

    Jan 5, 2010
    371
    25
    10
    i would like to do the same with visio and project pro too, but am unsure how to rearange the script for these.

    the links for the non key needed are on wzt
     
  8. stasio

    stasio MDL Expert

    May 3, 2007
    1,193
    1,144
    60
    Thanks,I found and dl.
    Now,how to activate?
     
  9. alexcd2k3

    alexcd2k3 MDL Novice

    May 27, 2007
    46
    0
    0

    Ok, tonight unistall 4734, install 4730 save my file , uninstall 4730 and install again 4734 whit my 2 saved files and run the cmd activation.
    TXXXXXX
     
  10. stuclark

    stuclark MDL Novice

    Mar 26, 2009
    32
    2
    0
    To get this to work, the tokens.dat and pkconfig files NOT ONLY have to come from your own system, but they ALSO HAVE TO come from the same version of beta 1.

    In other words, if you had installed the x86 version of beta 1, this activation method will ONLY work on the x86 version of RTM. If you install the x64 version of RTM and use the files from an x86 beta 1 installation, this activation WILL NOT WORK.
     
  11. bchat

    bchat MDL Smart Azz

    Nov 7, 2008
    1,720
    453
    60
    Thanks stuclark - this explains why I couldn't mine to work.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. stuclark

    stuclark MDL Novice

    Mar 26, 2009
    32
    2
    0
    Does anyone know if beta 1 / beta 2 was available as x64? I can't seem to find a link for it now...
     
  13. troels

    troels MDL Member

    May 20, 2007
    170
    30
    10
    It will - but use the token file from beta 2.
     
  14. Anakunda

    Anakunda MDL Senior Member

    Feb 6, 2010
    284
    12
    10
    Hello there, I'm still having problem activate the beta from MS's site
    Anytime I invoke change product key I get setup error message.
    Tried to install this beta several times and never succeed to invoke enter product key dialog.
    But I did on all previous Office installs. Just problem with the beta from Microsoft's site.
    Guess the ProfessionalPlus.exe installs 32bit version, while I previously had installed 64bit version. Does it matter?
    Moreover, the update service attempts to install some update for Office 2010, shall I accept it?
    Any solution how to get the registered token alternate way?
    The VB script command doesnot work either :wallbash:
     
  15. alexcd2k3

    alexcd2k3 MDL Novice

    May 27, 2007
    46
    0
    0
    #158 alexcd2k3, Feb 8, 2010
    Last edited: Feb 8, 2010
    dont work !!!!

    1 - Download the beta from Microsof, activate online and uninstall. (backup tokens and pkey...)
    2 - Clear registry and hard disk.
    3 - Install version 4734 volume x64 wzor
    4 - Run script "activate.cmd (like administrator)
    5 - restart office and see nag screen "please insert the code 25..."

    6- pleaseee help meeee !!!!!:worthy::worthy::worthy:
     
  16. solartricity

    solartricity MDL Novice

    Aug 1, 2009
    4
    0
    0
    What worked for me was installing 4514 (x86 it didn't matter), activating it, then saving the pkey and tokens to the script folder. After, uninstall 4514 and the reboot, you need to not only do a registry clean but you have to go into the registry with an editor (I use Reg Organizer) and completely delete the key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform (which has 21 sub keys). This was very important. Then install 4734 and use the script and use the script and done. Reg Organizer is good because it shows in the software records section leftover registry keys after an uninstall and OfficeSoftwareProtectionPlatform was still there after the complete uninstall of 4514. I even installed the x64 of 4734 and had no problem.
     
  17. alexcd2k3

    alexcd2k3 MDL Novice

    May 27, 2007
    46
    0
    0
    Ok I try and write tomorrow if it went well !
    Tx
    Alex