[注意] ☆升级安装的Vista，都无法使用各种破解软工具激活☆

bumble

☆升级安装的Vista，都无法使用各种破解软工具激活☆
现在我修正一下：
所有的 升级安装 ，
目前为止用Paradox或基于它而修改的各种破解法 都统统激不活！



对http://www.vistafans.com/thread-119691-1-1.html贴的一个修正.

不仅仅是非C盘升级安装了，而是所有升级安装（包括从C盘的升级）都统统不能够用现有的证书和产品系列号来软破解掉而激活。

全新安装的都能激活， 而所有升级安装的都不能激活。
（无论是不是从C盘的，感谢那些对俺予以指正的高手，他们不辞辛劳亲自动手从C升级安装，证明了C盘安装的XP或Vista用Softmod等也激不活，向指正俺的大虾表示敬意！）

就是这样了。

改天有时间试一下。

修改bios
或者买正版的就可以激活了

原帖由 坐看云起QD 于 2007-3-20 03:41 发表
改天有时间试一下。

原因是微软关于升级的政策规定跟全新安装不同所致.

各位有兴趣可以随便试, 比如拿你现在已经激活了的试,安装光盘也不用换, 就用你装的那张就行, 只要升了一次, 原来的PID马上失效, OEM机都是这样, Vista自己升一下自己都失效激不活了.

有的过去装XP的用户只买了升级安装本,这些升级版不准许全新安装, 但用它Vista自己升自己不会失效, 而新买的品牌机所装的Vista的PID显然跟升级版不同,不允许随便再用安装光盘升级的, 如果升级了, 可能由于有记录导致原有PID不行,必须按升级来处理了.

试验升级前,先把你原本备份吧, 比如你想用已激活的来试验, 别怪我没先提醒你, 只要你再进行了一次升级安装, 原来本已经激活的PID都不行了.

(另外,Paradox只要有64位证书和PID就可以激活64位版,今天我已经亲自证明了. 用一台装了64位本OEM电脑上的Vista,先用Paradox的BIOS Emulation程序导出DUP,查号程序查出原机PID,再用Paradox法装在另台64位组装机, 顺利激活. 另外也证实了Paradox的模拟器发布日期, 得到了Paradox模拟器作者的Email. 我不想跟某些大忽悠过不去. 所以也就顺带提一下拉,厚道人自不欺世也不欺人, 明眼善察者也自然会心领神会了.)

原帖由 abcrci 于 2007-3-20 20:40 发表
修改bios
或者买正版的就可以激活了

现在买一个OEM品牌机,比如HP的,里面装带的也肯定是正版了, 先已激活, 但同样不许你随意升级, 你如果擅自把它升了一次级, 立马再激不活了.  全新装跟升级装大不同哦,正版也如此.

用vista loader 2.0可以激活，我昨天测试过

原帖由 cedilla 于 2007-3-20 21:04 发表



原因是微软关于升级的政策规定跟全新安装不同所致.

各位有兴趣可以随便试, 比如拿你现在已经激活了的试,安装光盘也不用换, 就用你装的那张就行, 只要升了一次, 原来的PID马上失效, OEM机都是这样, Vis ...

可以64位????

64位可以,我上面说的明明白白, 验证过了,也发短信给你了
恕不再多费口舌了!

1.Paradox只能用于32位系统,说的很明白了,OEM BIOS Emulation Toolkit For Windows Vista x86 v1.0,64位根本不能用,麻烦看清楚是不是这个,还是把别的什么当作Paradox了

2.证书根本不分64位和32位!

如果说你用Paradox激活了64位系统,麻烦贴一张C盘抓图(要显示隐藏文件)包括已经激活的系统属性的图上来

论坛上几百人用那个都激活不了64位
偏偏你就可以
你用的绝对不是Paradox的OEM BIOS Emulation Toolkit

这个是原版工具里面的readme,哪里有说支持x64了??


                *************************************************************
                *** OEM BIOS Emulation Toolkit For Windows Vista x86 v1.0 ***
                *************************************************************


What's the purpose of this release?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Bypassing the product activation requirement of Microsoft Windows Vista x86.


How does it work?
~~~~~~~~~~~~~~~~~

Microsoft allows large hardware manufacturers (e.g. ASUS, HP, Dell) to ship their products
containing a Windows Vista installation that does NOT require any kind of product activation as
this might be considered an unnecessary inconvenience for the end-user.
Instead these so-called 'Royalty OEMs' are granted the right to embed certain license information
into their hardware products, which can be validated by Windows Vista to make obtaining further
activation information (online or by phone) obsolete.
This mechanism is commonly referred to as 'SLP 2.0' ('system-locked pre-installation 2.0') and
consists of the following three key elements:

1. The OEM's hardware-embedded BIOS ACPI_SLIC information signed by Microsoft.

2. A certificate issued by Microsoft that corresponds to the specific ACPI_SLIC information.

   The certificate is an XML file found on the OEM's installation/recovery media,
   ususally called something like 'oemname.xrm-ms'.

3. A special type of product key that corresponds to the installed edition of Windows Vista.

   This key can usually be obtained from some installation script found on the OEM's
   installation/recovery media or directly from a pre-installed OEM system.

If all three elements match Windows Vista's licensing mechansim considers the given
installation a valid system-locked pre-activated copy (that does not require any
additional product activation procedures).

So the basic concept of the tool at hand is to present any given BIOS ACPI_SLIC information to Windows
Vista's licensing mechanism by means of a device driver.
In combination with a matching product key and OEM certificate this allows for rendering any system
practically indistinguishable from a legit pre-activated system shipped by the respective OEM.


How do I use it?
~~~~~~~~~~~~~~~~

Preliminary hint:
Most operations described below require elevated privileges, so disabling UAC (Run->MSCONFIG.EXE->
Tools->Disable UAC) for the time being is recommended, Of course, it can be safely re-enabled after
all steps have been performed. Otherwise OEMTOOL.EXE and some SLMGR.VBS operations must be explicitly
run with adminstrative privileges.

1. Install the Windows Vista x86 edition of your choice without entering any product key during setup.
   Basically any Windows Vista x86 installation media will do, regardless if it's MSDN/Retail/OEM/...,
   MSDN/Retail are recommended though.

2. Install the emulation driver.

   Run OEMTOOL.EXE, select the OEM BIOS information to emulate (ASUS might be a good choice given the
   fact that it's the only OEM for which a complete set of product keys is provided ;)) and hit the
   '<Install Emulation Driver>' button.

   Alternatively you can just right-click the ROYAL.INF file and chose 'Install' from the appearing
   menu. This only allows for installing the default OEM BIOS information (ASUS) though and is strongly
   discouraged unless OEMTOOL.EXE fails for some unknown reason.

   When prompted about whether to install an unsigned driver, allow it.
   (For some odd reason Microsoft didn't wanna sign this one...;))

3. Reboot your machine.

4. Install the OEM certificate matching your OEM selection during driver installation by running

   SLMGR.VBS -ilc <OEMNAME>.XRM-MS

   (e.g. "SLMGR.VBS -ilc C:\ASUS.XRM-MS" if you chose to install the default driver and extracted
    the certificate file to C:\)

   Note that this operation might take quite a while depending on your system, so be patient.

5. Install an OEM product key matching the installed edition of Windows Vista x86 by running

   SLMGR.VBS -ipk <OEM_PRODUCT_KEY>

   (e.g. "SLMGR.VBS -ipk 6F2D7-2PCG6-YQQTB-FWK9V-932CC" if you're running Windows Vista Ultimate using
    the default emulation driver)

   Note that this operation might take quite a while depending on your system, so be patient.

   See PKEYS.TXT for a list of OEM product keys published by different OEMs.

6. Run 'SLMGR.VBS -dlv' or right-click 'Computer' and chose 'Properties' to verify your licensing status.

Due to the variety of possible combinations of different earlier Vista activation hacks we're not gonna
provide details on 'persuading' existing installations to accept this method.
During our test the general procedure depicted above worked out fine though, i.e. installing the emulation
driver, rebooting the machine and then using the officially documented ways of installing a matching OEM
certificate and product key should do the trick in all but the most messed up cases.


What's that '<Dump OEM BIOS Information>' button in OEMTOOL.EXE for?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It dumps the BIOS ACPI_SLIC information of any SLP 2.0-enabled OEM system.
The dump can consecutively be used to emulate ('clone') that information on any other system by specifying
the 'Custom' option.
Using this function on a system booted using the emulation driver will give a dump identical to the currently
emulated OEM BIOS information, so be sure to uninstall the driver and reboot the source machine first if you
intend to dump the actual hardware-embedded OEM BIOS data.


What are all those files for?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

DIFXAPI.DLL                        - a runtime dll for Microsoft's DIFx API used by oemtool.exe
OEMTOOL.EXE                        - an application for installing/uninstalling the emulation driver
                                    and dumping BIOS ACPI_SLIC information from any SLP 2.0-enabled
                                    Windows Vista OEM system
PKEYS.TXT                        - contains a list of validated OEM product keys
README.TXT                        - this file
ROYAL.INF                        - driver .INF file, can be (ab)used to install the emulation driver
                                    in case oemtool.exe fails to perform this task
ROYAL.SYS                        - the emulation device driver

CERTS\ACER.XRM-MS                - the certificate that corresponds to the ACPI_SLIC information
                                    emulated by the driver when 'Acer' has been selected during
                                    driver installation
CERTS\ASUS.XRM-MS                - the certificate that corresponds to the ACPI_SLIC information
                                    emulated by the driver when 'ASUS' has been selected during
                                    driver installation
CERTS\HEWLETT-PACKARD.XRM-MS        - the certificate that corresponds to the ACPI_SLIC information
                                    emulated by the driver when 'Hewlett-Packard' has been selected
                                    during driver installation
CERTS\LENOVO.XRM-MS                - the certificate that corresponds to the ACPI_SLIC information
                                    emulated by the driver when 'Lenovo' has been selected during
                                    driver installation



Enjoy,
TEAM PARADOX '07