Microsoft Office Professional Plus PT-BR x86 Trial, asks for the serial on installation, downloaded from M$.
SFX EXE, ISO, or extracted? (I can't seem to find a link to that version direct). PS: If it is extracted already you have to press Installer Path, not Extract Setup. The exception is being thrown for whatever reason because after detection, no entries are added to the comboboxes.
Can you extract it and show me a list of files/folders? As I said that exception is being thrown because for some reason the dialog boxes detected nothing. This could have happened by language or office sku, or something screwed up in extraction. And this is Pro Plus, not Pro right? Because if you have a SingleImage.WW folder, that installer is not supported.
OK that is not extracted in the way I meant but good enough. Delete that folder, and hit extract setup (not installer path) and select the DL'd EXE file that when you run it.
@Bosh if you are going to do UI work, just use the last version of the source you have. My FTP host is dead right now, and the code in question hasn't changed very much (except for 2.1.2 where I made a minor change). The current code is a bit current UI dependent. I can fix up the code to accomodate the UI changed @Anyone else Please give suggestions to help improve the Customize Setup Tab UI. I made that UI myself during the long pre-beta work for V2.1 and it hasn't really been thought about too much as other things have taken priority. We need these suggestions to help with the UI improvements as I myself can't really think of a way to improve it (That's why first order of business when we started V2.0 was for Bosh to make a UI, I'm better at back-end code than nice UI's).
Hi i have tested every version up to 2.1 , and i just tried 2.1.2 and read the changelog about fixing persistant 8000700D Errors in 2.1.1, and to my supprise 2.1.2 attemt to activate gives me persistant 8000700D Errors this is the first time it has ever done this to me with any version. please fix it i'm running windows 7 if thats any help to you. ERROR CODE: 0x8007000D <Product activation failed>
I don't want to get technical, but we knew this from the begining when me made the modification. And don't worry coz we can easily solve your problem. But we really appreciate it if you could give us some info. Did you have this problem with previous version as well? Could you please give us your CMID (KMS client machine ID )? If you don't know how to get it, here is the command: Code: cscript "%programfiles%\Microsoft Office\Office14\ospp.vbs" /dcmid P.S. : Don't worry, making your CMID public is not gonna get you into any trouble. It's not like MS can find you just by looking at it.
Hi here's my CMID and the last version i used was 2.1 i never used 2.1.1 but this is the problem since i tried 2.1.2 all other version 2.1 and before worked fine. hope u can fix it soon Code: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\USER>cscript "%programfiles%\Microsoft Office\Office14\ospp.vbs" /dcmid Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. ---Processing-------------------------- --------------------------------------- Client Machine ID (CMID): 3ce34d7f-906d-4451-ba8e-b0ac9471e8a7 --------------------------------------- ---Exiting----------------------------- C:\Users\USER> P.S I don't care if Bill Gates and his microsoft corporation knows where i live
letsgoawayhell I installed Office 2010 x64 on my Windows 7 HP N SP1 Heb edition and unfortunately I had the same persistant 0x8000700D error again, I tried with the original ZWT keygen over 50 times then restart and again tried for about 20 requests again with no go. THEN I tried your modded keygen and it worked right away! on the first try! really good job! I can confirm that it helps to anyone who may have the annoying 0x8000700D error. the things is that "rearm" will probably help to fix this error too, but I did not do a rearm because I wanted to test your modded keygen and it works. so really thank you for unveiling phanzar "secret". Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. ---Processing-------------------------- --------------------------------------- Installed product key detected - attempting to activate the following product: SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel Last 5 characters of installed product key: H3GVB <Product activation successful> --------------------------------------- --------------------------------------- ---Exiting----------------------------- EDIT: now it seems that if I use your modded keygen to reset the timer back to 180 days - it only works on the second try, the first try gives 0x8000700D error, is that normal? (with zwt original keygen it does not works at all, still gives 0x8000700D error no matter how many times I run cscript "%PROGRAMFILES(x86)%\Microsoft Office\Office14\ospp.vbs" /act ..) but hey it's working so I can confirm that your version is superior then zwt original keygen and it does indeed fix the 0x8000700D error.
Hi I haven't updated OTK since 2.1 beta 3 I'm not using any of the other capabilities of the toolkit except for the ez-activator and i haven't faced any of the errors that other users have mentioned (considering i have tested it a lot in different situations and different PCs) My question is, is there any necessity that i upgrade to version 2.1.2 ?
Yes, It is normal. Modification prevents that persistent error but you may need to try more than just 1 time. Sometimes you get that 0x8000700D error but it is not persistent. And you are welcome dude. MDL is a great place. I got to know a lot of great people and I learned a lot of great things here. It is an honor to contribute to the community. P.S. : It really helps if you gimme your KMS CMID too. But if you feel unsecure about it, it's OK I can understand.
Thanks for CMID. Don't worry, consider it fixed even right now. Glad you don't feel bad about giving it to us.