It really depends on system specs.
If the host already is rather slow, and the VM is running at barely minimum settings (ie VPC allocates XP only 256MB  RAM at default), it WILL take a very long time.
Also, enabling CPU virtualization support in both the host's BIOS as well as the VM's settings will gain you quite a lot.
Besides, a Virus Scanner running on either host and/or guest will slow things down considerably!
You may want to disable real-time protection for the installation.

IDK means, I don't Know.

listen, I can give 512Mb to a VM, and I can give it plenty processing power. It will still not be the same as real metal.
I have not used KTD for a while now, because DPinsT can replace that function, and, DPinsT can do this with updated DriverPacks, which is not a feature you will find in KTD (what you streamed and told windows is there is what is there..)

Thanks for answered,
IDK, it makes sense ... hehe f*** foreigners.

DPinsT, microsoft installer?
I will give a search and see what I find.
Know any link which I can begin?

thanks again

the time it takes to apply KTD depends on system speed as well.
Two hours seems long, but in a virtual machine, who knows.
If you reset while it is still churning and editing the registry... yikes.. I think that would spell trouble.

listen, I can give 512Mb to a VM, and I can give it plenty processing power. It will still not be the same as real metal.
I have not used KTD for a while now, because DPinsT can replace that function, and, DPinsT can do this with updated DriverPacks, which is not a feature you will find in KTD (what you streamed and told windows is there is what is there..)

Next thing I know somebody asks Warmsnow if he wants to write a KTD update module for DPinsT.
(and the cleanup of old drivers from the registered files in windows... aarh.)

anyway, I will run a KTD session in real metal, and see how that goes.

I do not follow you.

Is there any way to hasten the process?
Like, wait about 20 min. and reset the machine!

1 IDK...
2 method 2
3 No... there are registry entries and cache files that need to be added when the folder is populated.

I am new here and I have some doubts on DriverPacks 8.05.
Very nice piece of working software, keep it up.

let´s do it.
1- Which the estimated time for this Pack Finisher to apply the KTD?
   I am waiting  OVER 2:00 hours and nothing to finish (vmware testing).
   what´s wrong? Never had to wait this long before.

2- Which the best method of pattern for the DriverPack?
Method 1 or 2?

3- can I add more updated drivers to (%systemdir%\Driverpack) later on?

thanks.