V-Tools - toolkit for modifying all MS virtualization products

the latest version is not able to modify the vmwp.exe of windows 2012. I see that the file size is increasing by 200kb. and SLIC still shows MSFT 2.0. I tried to add dell 2.3. Anyone facing similar issue?

 

The Slic seems to work, I've tried a few SLP files with no luck.

 

Hi,FelixV
Today,I updated the system to win10 1709 and the vmchipset.dll file updated to 10.0.16299.15. I used V-Tools_1.3.0.21 Mod the vmchipset.dll file OK. But

it can not work. I can not start my VM. Jump the error window. say about the Digital signatures.....​

 

Hi

Is there any way to use these tools to update the DMI info in module 6 only?

I'm using Hyper-V's vmchipset_v10.0.15063.00413.dll file and I'd like to put in custom serial and product etc strings into Type 1. I've hex edited the extracted 06 bin file (from the multi mod) and manually replaced the module in mmtool2, and then replaced the resource in Resource Hacker with the new 13500.rom file, but when putting it back into system32, no VM will start. I'm guessing it's due to the "unlocking" of the BIOS bin to rom which I need to reverse.

Thanks

 

it seems this software dosen't work with 1703/1709.

was anyone successful?

 

I am amazed that it worked as long as that. Digital signature was not introduced last year, it was just MS that chose to ignore its requirement in Hyper-V
Seems no more...

 

Hi, thanks for your phantastic work. Any chance to implement a function to change the BGRT image? Greets

 

You need to login to view this posts content.

 

Hi there all

I am thinking about upgrading my server 2012r2 to 2016. I really liked the abilitiy to inject the slic tables into vmwp.exe in 2012. Does this tool still work for 2016? Are there any additional steps required? I don't want to upgrade without confirmation first. Any help would be greatly appreciated,

thanx
Craig

 

Been trying today to get it working on a 2016 server. No good so far.

Also, just updated my 2012 r2 and modded vmwp.exe from 12/2018, now no 2016 guest will start due to digital signature issue.

Any help would be appreciated.

 

在完成10%时，我也出现同样的问题
“
Display: Error allocating Memory.
There is a solution to this error:
”
在原有的中文下改成英文无效

 

Is there any updates here？In the latest hyper-v 2016, I can modify the file, but guest stuck at the Hyper-V logo.

 

I used an SLIC.bin and the Hyper V exe and when I perform a single mod it reports the error modificiation not performed. Any idea where it could be going wrong?

Edit: It seemed to work with the chipset.dll instead. However, that doesn’t seem to be enough. Running into the same signature issue as everyone else. If no one had found a way around it I suppose I can just use an OEM COA and export and import the machine as that should keep the virtual hardware the same when I need to move it. Someone correct me if I’m wrong on that.