Such As ???

I did find my key in APA - Thank You...
I went with v15...

I use MiniTool PW and Macrium...

Out of 285 Applications - I use a total of 22.......

APA > line 381 - stays as free version
-
ABU > would you prefer to know if serial was found and where or just not found
but we have to write both line to registry

v15 was listed as a "Testing" due to serial key process...................

As I stated v14 (Release) is an exact Match, except with out new key process.........

not sure any more what I am working with in ABU....
As I have 3 file locations.....

As v15 - seems to be an exact match to v14 - except v15 checks and informs if either registry serial key is found...
x86 writes in the standard location -- x64 writes in both locations... (As x64 was only writing ...

Tested both The Packing (Encoding) and The Extraction Process for both x86 & x64 - I can not verify your results...

v15 testing >> I added message to the location of where the key was found - if key not found in wow , then will look in the other

I created a message that pops up when the key is found...

ABU 7.4.1.0 and 8.0.0 both placed the serial in WoW6432Node and standard locations..

So appears it has been like that for a while......

I also know Holmes had to address the issue with serials in the wow6432node entry..

fixed 21:48
and PA ...

lines 445 & 447 appear duplicates to me (ver14)

that aint what you said before

Fixed..

we could change up this whole serial key thing and just write standard serial - if host serial does not exist...

I never liked that it save to interface.... i shared mine more then a few times because of it...

What you think?

fixed dup 273/274... 436/438 dup not exist on mine. (but I am a version ahead of you with edits)

If,%Architecture%,Equal,x86,Set,%wow6432Node%,""
Else,Set,%wow6432Node%,Wow6432Node\

Tmp_Software\%wow6432Node%Microsoft\Windows

for the x64 software it would write > Tmp_Software\wow6432Node ...

Here is the Deal which you never figured out.... You update for yourself, We update for everybody else...
I do not post updated Container files or post 7z Packs with empty ones...
So even though the Script Supports v8 - it also "still" supports existing Container files, that have not been updated ...

Understand that fully.. As I only have x64 PC's now, So can not boot x86 to test.. Thus i kinda dropped support for x86 systems, in my testing (development)

The final version includes both QT4 & QT5 files...

Now here "was" the problem - v8 uses QT5 and prior uses QT4.....
The older versions will no longer work with the current (12) edits....
So either they must be included in one script or be two separate scripts...
Having both does not effect the extraction process ( if not there then not extracted ...

%GTarget%=%BaseDir%\Target

I did 64 x64 and then go into advanced menu and save the reg file - then add the Reg to Build...

There is no way in Hell, anyone needs all those Applications.....
Other then doing it because you can...

New Version of innounp (2.62.1) released 3 Days Ago
CrystalDiskInfo has usually been the first indicator

Actually when running any of the PE Builder Projects - you should add an "Exception" to your Anti-Virus Software for the Whole Project Folder...
Thus allowing the Project to run without Virus scanning....
I would think that if you are using the Project and commenting to the Developer - there is a ...

if "hiberfil.sys" is present on the root of a drive - simply delete it... Problem solved..