Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - JFX

Pages: [1] 2 3 ... 25
Finally, version 17.04 is ready and online.

And now look at this Antivirus scan for GetWaikTools  :cool:

So everyone who get's an false positive in future, stop posting it here
but send a complaint to your Antivirus company.

Win10PE SE HomePage / Re: Hyper-V Crash "Testing ISO as CD File"
« on: April 18, 2017, 10:44:07 PM »

So if someone is writing a replacement builder, why not change the syntax as well. Sure, it will break everybodies projects including mine, but it also gives a lot of new and better commands.

Just my 2 cents. :wink:
Totally agree. The syntax of WB is also one of it's main problems.
LSP mostly inherit this style and soon there will be another builder with this silly synatx  :frusty:

Exclude the WinPESE directory in your Symantec Endpoint Protection.

Win10PE SE HomePage / Re: Will Win10PE SE Support 15063 Build?
« on: April 14, 2017, 09:22:41 PM »
Ahh, you right seems RS2 creates REFS v3.2 volumes and 14393 drivers only support it up to version 3.1.

Win10PE SE HomePage / Re: Will Win10PE SE Support 15063 Build?
« on: April 11, 2017, 01:13:37 AM »
Win10PE_SE already supports REFS, you can read and also create a REFS partition with Win10PE_SE 14393.

There is no virus. If you encounter such messages from your AV than check it on VirusTotal

Also send the file to symantec  and ask them to fix their product.

Win10PE SE HomePage / Re: Will Win10PE SE Support 15063 Build?
« on: April 06, 2017, 07:39:10 AM »
There is actually just one problem, it's not stable.
On Windows 10 RS1 I get 1 or 2 app crashes a week, well actually that great for everyting that comes after Windows 7.

However on this new RTM, I have crashes every couple of hours.
Left alone the hidden ones, you only noticed looking at the event log.
Specially explorer hangs and crashes are very annoying.

On ADK side they messed up the wofadk.sys driver, it can no longer works under Windows 7. Just like they did with bcdedit.exe.
Also you properly noticed the system context menu "New" sub menu in the new WinPE.
Well, it freeze because it now depends on the StateRepository service.

We can get it to work on WinPE, but will need a workaround because it 's not fully compatible with the FBWF used in WinPE.

Win10PE SE HomePage / Re: Will Win10PE SE Support 15063 Build?
« on: April 06, 2017, 05:15:09 AM »
It properly will be be supported in future, like it happened with the previous versions before  :rolleyes:
Have a strong feeling that there will soon come some refresh ISO, as 15063.0 is pretty much a disaster.

For WAIK I don't intend to update to the even buggier 15063 version unless there is any reason.

Hi Noel,

Good weather here, so I'm not going into the headache of why WinPE not sends this message.
I've updated my WinPE loader to fire this message on every time it receives a wm_taskbarcreated message.
This seems to be a perfect solution.

Yes it's IDA 6.8 with loaded x64 explorer.exe version 14393.

I guess the CTray object has it's own function to enable\disable the show desktop functionallity.

You rock man  :thumbup:

Seems it's explorer himself who send this message.


Questions and Support / Re: SysWoW64 - some observations
« on: March 23, 2017, 12:58:39 AM »
Hi Misty,

They should not be replaced, but could be added.
But there is no need. SMI key is handled by SxS_Unknow Section of the WoW64 Plugin.

IA64 is an old architecture already superseded by AMD64.

ARM and ARM64 are very new architectures. You can ignore them for now.
It see Microsoft does not really know what they want with ARM and their Windows RT version.

Questions and Support / Re: SysWoW64 - some observations
« on: March 22, 2017, 07:55:59 AM »
By SxS error always check the manifest of an application.

This DMDE version 3.2 properly need a newer VCRuntime-

Questions and Support / Re: SysWoW64 - some observations
« on: March 22, 2017, 06:48:25 AM »
Hi misty,

Microsoft is moving a lot of code into *base.dll or *.core.dll files.
To have a good application compatibility you should add all of them to your WinPE.

Hmm, will be difficult to find it for other version.
Would be easier if we could find the reason why this byte is set in WinPE.

Great work Noel  :thumbsup:

For x86 it's *CTrayObj + 0x231


good news today on a new Windows 10 RS2 machine, I could reproduce all problems.
The memory patching of wimgapi.dll used by the winload extraction causes quite some memory corruption
and leads to strange results. Actually I wonder why I does not crash.

For the percent progress, it's really a math problem.
The language have no unsigned integer, so I have to change quite a bit.

I couldn't really reproduce the this locked folder problem you mentioned. But so far the x64 version is now fully working here.

Pages: [1] 2 3 ... 25
Powered by EzPortal