Jump to content











Photo
* * * * * 1 votes

files required to get a) drag drop and b) file copy progress working in PE


  • Please log in to reply
86 replies to this topic

#51 stayboogy

stayboogy

    Member

  • Members
  • 47 posts
  •  
    United States

Posted 02 February 2018 - 12:45 AM

I must add I am not using MistyPE - just doing it manually using ADK - I have just repeated process using ADK v1709 and getting additional files from a Windows 10 1709 install.wim - and again file copy progress dialog works fine for me when testing it in explorer++

 

All I am doing is creating basic PE using ADK, mounting boot.wim and copying two files from above into system32 (I am getting files from a install.wim from same windows 10 build version)

 

Once booted I then double click reg file containing above registry keys, run Explorer++ and copy progress works

maybe the difference is something in the 1709 source as i am using 1703



#52 misty

misty

    Gold Member

  • Developer
  • 1035 posts
  •  
    United Kingdom

Posted 02 February 2018 - 01:02 AM

@stayboogy

I've been noticing some strange results when actxprxy.dll settings are added to the registry during the build process. For some reason, despite the settings being present in the registry, the File Progress dialog is not working. Running regsvr32 /s actxprxy.dll (in winpeshl.ini or when WinPE is running) resolved the issue. Give it a try - and please report back.

 

:cheers:

 

Misty



#53 stayboogy

stayboogy

    Member

  • Members
  • 47 posts
  •  
    United States

Posted 04 February 2018 - 09:11 PM

@stayboogy

I've been noticing some strange results when actxprxy.dll settings are added to the registry during the build process. For some reason, despite the settings being present in the registry, the File Progress dialog is not working. Running regsvr32 /s actxprxy.dll (in winpeshl.ini or when WinPE is running) resolved the issue. Give it a try - and please report back.

 

:cheers:

 

Misty

 

thanks.  testing now.



#54 stayboogy

stayboogy

    Member

  • Members
  • 47 posts
  •  
    United States

Posted 04 February 2018 - 09:37 PM

still not working.

 

i added that to my registryadd.cmd that runs at boot called from winpeshl.ini

 

i also manually ran it from command prompt in booted winpe and still no copy progress dialogue.



#55 slore

slore

    Member

  • Members
  • 51 posts
  •  
    China

Posted 05 February 2018 - 11:00 AM

still not working.

 

i added that to my registryadd.cmd that runs at boot called from winpeshl.ini

 

i also manually ran it from command prompt in booted winpe and still no copy progress dialogue.

 

why not think about the progress of how the identified dependencies found out?

 

I already told for the v1609 is no need the OneCoreUAPCommonProxyStub.dll

 

but actxprxy.dll + chartv.dll + REG(actxprxy.dll's CLSID and INTERFACE).

 

WIN10PESE v1703 has no OneCoreUAPCommonProxyStub.dll, so it must wrong for v1703.

 

COPY INSTALL.WIM's actxprxy.dll + chartv.dll + config\SOFTWARE

 

I think your PE will work.

 

minimal list IF can be a conjecture:

 

load install.wim(v1703)'s SOFTWARE and search the  "IOperationsProgressDialog".

you will got:

 

[HKEY_LOCAL_MACHINE\PE\Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C}]
@="IOperationsProgressDialog"
 
[HKEY_LOCAL_MACHINE\PE\Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C}\ProxyStubClsid32]
@="{C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6}"
 
YOU CAN SEE the class ID is different.
 
so, search the class ID in CLSID, you will got:
 
[HKEY_LOCAL_MACHINE\PE\Classes\CLSID\{C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6}]
@="PSFactoryBuffer"


[HKEY_LOCAL_MACHINE\PE\Classes\CLSID\{C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6}\InProcServer32]
@="X:\\Windows\\System32\\ActXPrxy.dll"
"ThreadingModel"="Both"

it is actxprxy.dll not the OneCoreUAPCommonProxyStub.dll.

 

add actxprxy.dll + chartv.dll + actxprxy.dll's CLSID + Interface with "{C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6}"

 

should be work.

 

Form the name OneCoreUAPCommonProxyStub.dll, actxprxy.dll, I think MS make some spilt separate the

actxprxy.dll's some function to OneCoreUAPCommonProxyStub.dll.

 

sorry for I don't have time to download the v1703 version and test this.

Please TRY this by yourself, and feedback.


  • darren rose likes this

#56 misty

misty

    Gold Member

  • Developer
  • 1035 posts
  •  
    United Kingdom

Posted 05 February 2018 - 11:43 AM

@slore
Very nice post on finding the dependencies.

WIN10PESE v1703 has no OneCoreUAPCommonProxyStub.dll, so it must wrong for v1703.


The Win10PESE v1703 project may not have it, but the OneCoreUAPCommonProxyStub.dll file is present in Windows 10.0.15063 (Build 1703).

In my own project the File Copy Progress dialog was not working previously with 1703 sources, but appears to be with the registry entries for OneCoreUAPCommonProxyStub.dll posted in this topic.

I do not have time to retest at the moment. I'll try and verify this later.

Misty

#57 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 449 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 05 February 2018 - 01:41 PM

still not working.

 

i added that to my registryadd.cmd that runs at boot called from winpeshl.ini

 

i also manually ran it from command prompt in booted winpe and still no copy progress dialogue.

 

@stayboogy

 

My suggestion would be to use 1709 rather than 1703 - then at least we are all using/testing with same sources

 

Then the information from Slore (and Misty) earlier in thread works fine to get progress dialog working - I have repeated from scratch many times now and those instructions are definitely correct for 1709

 
 
FILES TO ADD:-
 
Windows\System32\chartv.dll
Windows\System32\OneCoreUAPCommonProxyStub.dll
 
REGISTRY TO ADD:-
 
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341}]
@="PSFactoryBuffer"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341}\InProcServer32]
@="x:\\Windows\\System32\\OneCoreUAPCommonProxyStub.dll"
"ThreadingModel"="Both"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{036B4FC7-6A11-4C07-8046-22D268C37721}]
@="IInterruptedOperationHandler"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{036B4FC7-6A11-4C07-8046-22D268C37721}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{04B0F1A7-9490-44BC-96E1-4296A31252E2}]
@="IFileOperationProgressSink"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{04B0F1A7-9490-44BC-96E1-4296A31252E2}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C}]
@="IOperationsProgressDialog"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{4AE7498C-E1C0-475F-8573-41C26127C5D8}]
@="IOperationStatusTile"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{4AE7498C-E1C0-475F-8573-41C26127C5D8}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{61A969EF-64EA-4C48-BBF5-EEDE3B32BF86}]
@="IOperationStatusService"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{61A969EF-64EA-4C48-BBF5-EEDE3B32BF86}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"


#58 misty

misty

    Gold Member

  • Developer
  • 1035 posts
  •  
    United Kingdom

Posted 05 February 2018 - 02:39 PM

@stayboogy
I've retested and you are correct - the File Copy Progress dialog is not working in Windows 10.0.15063 (Build 1703) versions of WinPE.

Using a basic WinPE with nothing else added I have not been able to get the feature working. I mentioned previously that I only have 64-bit source files available. It looks like in my previous test I had enabled SysWoW64 support in my build. With SysWoW64 support added to the same WinPE the file copy progress function does appear to be working. This is a little bit bizarre.

Please accept my apologies.

Regards,

Misty
  • stayboogy likes this

#59 misty

misty

    Gold Member

  • Developer
  • 1035 posts
  •  
    United Kingdom

Posted 05 February 2018 - 03:29 PM

Quick test - the file copy progress dialog is working if the full Classes\Interface key is imported from the software hive in install.wim.

This is a dirty hack and the majority of the Classes\Interface subkeys are unlikely to be required. gsar is reporting 485 matches to {C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6} in the .reg file created when the Classes\Interface key was exported (out of 44681 keys in the registry file).

I'm not in a position to trace the registry dependencies at the moment.

Misty
  • slore likes this

#60 stayboogy

stayboogy

    Member

  • Members
  • 47 posts
  •  
    United States

Posted 07 February 2018 - 01:03 AM

Quick test - the file copy progress dialog is working if the full Classes\Interface key is imported from the software hive in install.wim.

This is a dirty hack and the majority of the Classes\Interface subkeys are unlikely to be required. gsar is reporting 485 matches to {C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6} in the .reg file created when the Classes\Interface key was exported (out of 44681 keys in the registry file).

I'm not in a position to trace the registry dependencies at the moment.

Misty

 

Thanks Misty

 

 

so i mounted the install.wim software.hiv, exported the classes/inteface key to a hiv file

 

then i mounted the winpe.wim software.hiv, and then ran "reg restore HKLM\PEREGISTRY\Classes\Interface C:\interface.hiv"

 

and viola, the entire classes/interface key was copied over the original key in winpe and now copy progress dialogue works

 

{the reason i added how imported the keys was to show how unneeded OfflineReg is as a tool as windows already has the tools necessary to do the job}

 

if someone could figure out which keys are actually needed that would be great.  i specifically needed this in x86 builds because x86 will boot off anything which makes x64 absolutely useless for me for anything, and in general too...
 


Edited by stayboogy, 07 February 2018 - 01:03 AM.


#61 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15341 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 07 February 2018 - 10:01 AM

 

then i mounted the winpe.wim software.hiv, and then ran "reg restore HKLM\PEREGISTRY\Classes\Interface C:\interface.hiv"

 

and viola, the entire classes/interface key was copied over the original key in winpe and now copy progress dialogue works

 

{the reason i added how imported the keys was to show how unneeded OfflineReg is as a tool as windows already has the tools necessary to do the job}

 

Very nice of you indeed :) to show your appreciation for the hard work by erwan.l (and by Misty for the documentation and troubleshooting).

 

For the record only:

 

Case #1:

You mount to an online Registry a hive and then import either some .reg or .hiv file.

Murphy's Law applies, one of the paths/settings in the .reg or .hiv file is wrong and affects the online Registry, potentially (within Murphy's Law realms this translates to surely ;) )crashing the running system.

 

Case #2:

You import the same settings to an offline Registry.

Murphy's Law applies, one of the paths/settings in the .reg or .hiv file is wrong and affects the offline Registry, at the most the such modified hive won't work when you attempt to boot the PE.

 

Choice (and the possibility to have it) is good.  :thumbup:

 

:duff:

Wonko



#62 misty

misty

    Gold Member

  • Developer
  • 1035 posts
  •  
    United Kingdom

Posted 11 February 2018 - 08:57 AM

I've done some further investigation using Windows 10.0.15063 (Build 1703) sources and could not reproduce my earlier reports of success based on information in posts #58 and #59.

I am going to blame a lack of sleep for this (again) - the information I posted in posts #58 and #59 is incorrect.

The file copy dialog does in fact appear to require OneCoreUAPCommonProxyStub.dll. The settings are very similar to the information posted by slore ( :worship:) in post #29.

The GUID for the IOperationStatusService key is different in the different builds (1703 and 1709) -
  • {61A969EF-64EA-4C48-BBF5-EEDE3B32BF86} - 1709
  • {0C3C904A-AD89-4851-9C3D-210C080CEE18} - 1703
Full entries that work in both 1703 and 1709 builds -

.reg entries
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341}]
@="PSFactoryBuffer"

;hex value - %SystemRoot%\System32\OneCoreUAPCommonProxyStub.dll
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,4f,00,6e,00,\
  65,00,43,00,6f,00,72,00,65,00,55,00,41,00,50,00,43,00,6f,00,6d,00,6d,00,6f,\
  00,6e,00,50,00,72,00,6f,00,78,00,79,00,53,00,74,00,75,00,62,00,2e,00,64,00,\
  6c,00,6c,00,00,00
"ThreadingModel"="Both"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{036B4FC7-6A11-4C07-8046-22D268C37721}]
@="IInterruptedOperationHandler"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{036B4FC7-6A11-4C07-8046-22D268C37721}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{04B0F1A7-9490-44BC-96E1-4296A31252E2}]
@="IFileOperationProgressSink"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{04B0F1A7-9490-44BC-96E1-4296A31252E2}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C}]
@="IOperationsProgressDialog"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{4AE7498C-E1C0-475F-8573-41C26127C5D8}]
@="IOperationStatusTile"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{4AE7498C-E1C0-475F-8573-41C26127C5D8}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

;Windows 10.0.16299 (Build 1709) "IOperationStatusService" key 
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{61A969EF-64EA-4C48-BBF5-EEDE3B32BF86}]
@="IOperationStatusService"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{61A969EF-64EA-4C48-BBF5-EEDE3B32BF86}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

;Windows 10.0.15063 (Build 1703) "IOperationStatusService" key 
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{0C3C904A-AD89-4851-9C3D-210C080CEE18}] 
@="IOperationStatusService" 

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{0C3C904A-AD89-4851-9C3D-210C080CEE18}\ProxyStubClsid32] 
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}" 
.
OfflineReg entries (for use with the run command - e.g. add to commands.txt and run
"offlinereg D:\PATH\Windows\System32\config\SOFTWARE " " run commands.txt)
Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341} setvalue " " PSFactoryBuffer
Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341}\InProcServer32 setvalue " " "%SystemRoot%\System32\OneCoreUAPCommonProxyStub.dll" 2
Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341}\InProcServer32 setvalue "ThreadingModel" "Both"
Classes\Interface\{036B4FC7-6A11-4C07-8046-22D268C37721} setvalue " " "IInterruptedOperationHandler"
Classes\Interface\{036B4FC7-6A11-4C07-8046-22D268C37721}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
Classes\Interface\{04B0F1A7-9490-44BC-96E1-4296A31252E2} setvalue " " "IFileOperationProgressSink"
Classes\Interface\{04B0F1A7-9490-44BC-96E1-4296A31252E2}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C} setvalue " " "IOperationsProgressDialog"
Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
Classes\Interface\{4AE7498C-E1C0-475F-8573-41C26127C5D8} setvalue " " "IOperationStatusTile"
Classes\Interface\{4AE7498C-E1C0-475F-8573-41C26127C5D8}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
Classes\Interface\{61A969EF-64EA-4C48-BBF5-EEDE3B32BF86} setvalue " " "IOperationStatusService"
Classes\Interface\{61A969EF-64EA-4C48-BBF5-EEDE3B32BF86}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
Classes\Interface\{0C3C904A-AD89-4851-9C3D-210C080CEE18} setvalue " " "IOperationStatusService"
Classes\Interface\{0C3C904A-AD89-4851-9C3D-210C080CEE18}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
.
:cheers:

Misty
  • darren rose likes this

#63 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15341 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 11 February 2018 - 10:47 AM

...

I am going to blame a lack of sleep for this  ...

 

 

If it helps, I read at first "I am going to lame a black sheep for this ..." :w00t:

 

.. I also need  some sleep ... ;)

 

:duff:

Wonko


  • misty likes this

#64 stayboogy

stayboogy

    Member

  • Members
  • 47 posts
  •  
    United States

Posted 16 February 2018 - 01:44 AM

I've done some further investigation using Windows 10.0.15063 (Build 1703) sources and could not reproduce my earlier reports of success based on information in posts #58 and #59.

I am going to blame a lack of sleep for this (again) - the information I posted in posts #58 and #59 is incorrect.

The file copy dialog does in fact appear to require OneCoreUAPCommonProxyStub.dll. The settings are very similar to the information posted by slore ( :worship:) in post #29.

The GUID for the IOperationStatusService key is different in the different builds (1703 and 1709) -

  • {61A969EF-64EA-4C48-BBF5-EEDE3B32BF86} - 1709
  • {0C3C904A-AD89-4851-9C3D-210C080CEE18} - 1703
Full entries that work in both 1703 and 1709 builds -

.reg entries
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341}]
@="PSFactoryBuffer"

;hex value - %SystemRoot%\System32\OneCoreUAPCommonProxyStub.dll
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,4f,00,6e,00,\
  65,00,43,00,6f,00,72,00,65,00,55,00,41,00,50,00,43,00,6f,00,6d,00,6d,00,6f,\
  00,6e,00,50,00,72,00,6f,00,78,00,79,00,53,00,74,00,75,00,62,00,2e,00,64,00,\
  6c,00,6c,00,00,00
"ThreadingModel"="Both"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{036B4FC7-6A11-4C07-8046-22D268C37721}]
@="IInterruptedOperationHandler"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{036B4FC7-6A11-4C07-8046-22D268C37721}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{04B0F1A7-9490-44BC-96E1-4296A31252E2}]
@="IFileOperationProgressSink"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{04B0F1A7-9490-44BC-96E1-4296A31252E2}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C}]
@="IOperationsProgressDialog"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{4AE7498C-E1C0-475F-8573-41C26127C5D8}]
@="IOperationStatusTile"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{4AE7498C-E1C0-475F-8573-41C26127C5D8}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

;Windows 10.0.16299 (Build 1709) "IOperationStatusService" key 
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{61A969EF-64EA-4C48-BBF5-EEDE3B32BF86}]
@="IOperationStatusService"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{61A969EF-64EA-4C48-BBF5-EEDE3B32BF86}\ProxyStubClsid32]
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}"

;Windows 10.0.15063 (Build 1703) "IOperationStatusService" key 
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{0C3C904A-AD89-4851-9C3D-210C080CEE18}] 
@="IOperationStatusService" 

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{0C3C904A-AD89-4851-9C3D-210C080CEE18}\ProxyStubClsid32] 
@="{95E15D0A-66E6-93D9-C53C-76E6219D3341}" 
.
OfflineReg entries (for use with the run command - e.g. add to commands.txt and run
"offlinereg D:\PATH\Windows\System32\config\SOFTWARE " " run commands.txt)
Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341} setvalue " " PSFactoryBuffer
Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341}\InProcServer32 setvalue " " "%SystemRoot%\System32\OneCoreUAPCommonProxyStub.dll" 2
Classes\CLSID\{95E15D0A-66E6-93D9-C53C-76E6219D3341}\InProcServer32 setvalue "ThreadingModel" "Both"
Classes\Interface\{036B4FC7-6A11-4C07-8046-22D268C37721} setvalue " " "IInterruptedOperationHandler"
Classes\Interface\{036B4FC7-6A11-4C07-8046-22D268C37721}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
Classes\Interface\{04B0F1A7-9490-44BC-96E1-4296A31252E2} setvalue " " "IFileOperationProgressSink"
Classes\Interface\{04B0F1A7-9490-44BC-96E1-4296A31252E2}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C} setvalue " " "IOperationsProgressDialog"
Classes\Interface\{0C9FB851-E5C9-43EB-A370-F0677B13874C}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
Classes\Interface\{4AE7498C-E1C0-475F-8573-41C26127C5D8} setvalue " " "IOperationStatusTile"
Classes\Interface\{4AE7498C-E1C0-475F-8573-41C26127C5D8}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
Classes\Interface\{61A969EF-64EA-4C48-BBF5-EEDE3B32BF86} setvalue " " "IOperationStatusService"
Classes\Interface\{61A969EF-64EA-4C48-BBF5-EEDE3B32BF86}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
Classes\Interface\{0C3C904A-AD89-4851-9C3D-210C080CEE18} setvalue " " "IOperationStatusService"
Classes\Interface\{0C3C904A-AD89-4851-9C3D-210C080CEE18}\ProxyStubClsid32 setvalue " " "{95E15D0A-66E6-93D9-C53C-76E6219D3341}"
.
:cheers:

Misty

 

 

i confirm this works perfectly.  thanks Misty.



#65 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 449 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 21 February 2018 - 02:38 PM

I haven't noticed any issues resulting from the removal of WallpaperHost.exe. Thanks again for your suggestion - works like a charm.

 

Hi Misty, ALL

 

Anyone else having this issue when file copy progress dialog showing on screen e.g. as per image I am getting a ghost outline of a larger window appearing, and then just before file copy progress finishes it disappears

 

Not sure if perhaps related to getting rid of WallpaperHost.exe?

 

Just curious if just me or others getting it too

 

Tried various other "explorers" and does it for all, so not related to tool I am using at time

 

Attached File  ghost.jpg   139.66KB   0 downloads



#66 stayboogy

stayboogy

    Member

  • Members
  • 47 posts
  •  
    United States

Posted 22 February 2018 - 11:15 PM

Hi Misty, ALL

 

Anyone else having this issue when file copy progress dialog showing on screen e.g. as per image I am getting a ghost outline of a larger window appearing, and then just before file copy progress finishes it disappears

 

Not sure if perhaps related to getting rid of WallpaperHost.exe?

 

Just curious if just me or others getting it too

 

Tried various other "explorers" and does it for all, so not related to tool I am using at time

 

attachicon.gifghost.jpg

same happens for me, but only when i'm running a program windowed.  if it is running maximized and selected the copy progress shows without the outline of another window.

 

wallpaperhost.exe is removed from my builds.



#67 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 449 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 23 February 2018 - 02:53 PM

Thanks for reply, very interesting - for me some apps like Explorer++ full screen you are correct it doesn't do it, but for others it still does

 

Will have to try putting wallpaperhost.exe back and see if it is related



#68 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 449 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 23 February 2018 - 03:12 PM

okay I can confirm it has nothing to do with wallpaperhost.exe as does it whether present or not



#69 ericgl

ericgl

    Frequent Member

  • Expert
  • 323 posts
  •  
    Israel

Posted 09 April 2020 - 05:37 PM

Interesting findings in this thread.

I already have a WinPE10 b10586 x64 with Explorer shell working rather OK, which I created using WinBuilder a few years ago.

But this time I wanna try by myself on a fresh boot.wim from the ADK.
And of course, I have a full installation media of Win10 b18995 x64 - the source for adding files and reg settings to the WinPE boot.wim.

I'm gonna try some of the aforementioned ideas on a WinPE10 b18995.1 x64 en-US (boot.wim from ADK).
My goals are:

  • Working Windows Explorer shell with Taskbar & Start Menu (without screen glitches).
  • Working file transfer progress dialog.
  • Working Drag & Drop functionality
  • Working audio functionality
  • Use only internal files without 3rd party executables.
  • Document all changes made, and publish a proper guide, once I succeed with above goals.
  • WoW64 (32bit app support), networking & printing are currently not on the TODO list.

I already discovered that at least one CLSID key needs to be modified for this build (18995):
wrong key: 61A969EF-64EA-4C48-BBF5-EEDE3B32BF86
correct key: 6D5174EC-F425-4CD9-8643-CF36042987F1

After adding all the necessary files and reg keys as mentioned here previously, file transfer progress dialog and Drag&Drop are still NOT working, but:
In HKLM\WINPE_SW\Microsoft\Ole\Extensions:
The value "DragDropHost" points to {228826af-02e1-4226-a9e0-99a855e455a6}

So I've added the reg key to WinPE10 (offline, by loading the hive):
HKLM\WINPE_SW\Classes\CLSID\{228826af-02e1-4226-a9e0-99a855e455a6}

EDIT 1: I've also added many other files that seem to be important for Windows functionality, and for 3rd party apps that I use.
I did manage to get a working font selection dialog (for Notepad, for example) - at least that's some progress...

 

EDIT 2: It seems I have Drag&Drop working now. The file transfer dialog works, but only with Drag&Drop. If I click Copy, then Paste the file - no dialog appears.



#70 noel

noel

    Frequent Member

  • Advanced user
  • 137 posts
  • Location:nantes
  •  
    France

Posted 10 April 2020 - 03:39 PM

hi ericgl,

do your goal and philosophy require you to surgically identify, with precision, every necessary key?
For my part, I am retired, do not understand English very well. I build to occupy my free time winpe by adding features like WPD protocol, printers, bluetooth (partly)..
But I use another method: I use the entire software hive of the W10 reference. The size of the boot.wim file is a little larger but I can focus my research on other aspects of Winpe.
This is another track that may not suit you, I fully understand that. But it remains widely used when size is not an important criterion.
Greetings



#71 ericgl

ericgl

    Frequent Member

  • Expert
  • 323 posts
  •  
    Israel

Posted 14 April 2020 - 11:27 AM

The entire SOFTWARE hive of Win10 b18995 x64 is 63.5MB.

Sure, adding it in its entirety may solve many problems.

But, yes, I'm trying to be as surgical as possible, and to get the understanding of dependencies and such.

I've documented every file and registry setting that was added/removed/modified.

 

-----

In the meanwhile, I have built another WinPE10, from a newer source - Win10 b19592 x64, using ChrisR's WinBuilder Win10XPE.

This one has properly working:

  • GUI - Windows Explorer shell (with dark mode enabled)
  • File transfer dialogs and Drag&Drop working as expected
  • 32bit app support (WoW64)
  • Audio/Sound playback
  • Video Playback (tested H.264 and H.265 codecs in MP4/MKV/MOV containers)
  • LAN & WLAN Networking
  • Graphics driver with max resolution support
  • Firefox/Chrome Browsers (you can choose whether to include them in the WIM file or outside on the USB drive)

I have further modified it heavily to suit my needs and preferences (mouse cursors, date/time formats, taskbar and desktop shortcuts, etc...)

No doubt, it's very comfortable to use and work with.

There are 2 caveats though:

  1. It uses 3rd party apps to get all this juicy stuff working (PECMD.exe, SetWG.exe, nircmd.exe, mpg123.exe, FixScreen.exe, LetterSwap.exe, PinUtil.exe, Notepad2.exe, etc...). These are all freeware apps, open source or otherwise, but I would have liked to get the functionality using the source files only.
  2. The WIM file size of this WINPE10 x64 has grown to almost 1GB in size. It includes some essential apps which I chose to include inside the WIM. It still boots fairly quickly with a USB3.0 USB drive, but ideally I would like the WIM file to be under 500MB.

One of the things I've noticed is that with newer builds of Win10, some source files are now larger.
It is inevitable that building WinPE with newer builds will result in a larger WIM file size.

For example - the base WIM file size of WinPE x64 b19592 in the ADK is larger compared to, say, the WIM file of the base WinPE x64 b10586 due to the newer source files being larger, and also entirely new files that did not exist previously in the older build.

People who are trying to get a lean low-filesize WinPE to boot from should keep using older builds of Win10 for now, as most of the purposes for using WinPE - should still work fine. I need both, so I have multiple WinPE versions, old and new, with or without GUI.

With the light-weight WinPE (without GUI, fast boot time) - I have very specific purposes.
The WinPE with the GUI is more for general use and replacement for internal drive.



#72 noel

noel

    Frequent Member

  • Advanced user
  • 137 posts
  • Location:nantes
  •  
    France

Posted 14 April 2020 - 12:19 PM

 

It uses 3rd party apps

I understand you. And in my winpe made by my hands,i replace all these app by .... scripts Powershell with Dotnet. So, the size on my boot.wim is 878kb, near 1Gb.

i use IE, printers, WPD-MTP, a part of BTH....Only MS's app. Also, i use the result of some research made by other people like the change in LSM.EXE that you can see here https://github.com/N...aster/LSMHookerbecause the other forbiden site is broken ( i don't use his app, i use only the result, i change the code with a script PS).

 

But it's a long way to replace these app : they give 'a lot of comfort' and aesthetics.

 

I'm glad that other people are interested in building a winpe by their own hands. And it's a lot of fun when winpe grows.  And this is how knowledge can spread.



#73 paraglider

paraglider

    Gold Member

  • .script developer
  • 1739 posts
  • Location:NC,USA
  •  
    United States

Posted 15 April 2020 - 11:39 AM

Have you managed to connect bluetooth low energy devices ( keyboards / mice ) without using the device connection metro UI from settings? As far as I could work out MS does not provide an API for that. Classic API only appears to support older bluetooth devices.



#74 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15341 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 15 April 2020 - 12:36 PM

[OT]

Hey, paraglider, it is good to see you around

[/OT]

 

:cheers:

Wonko



#75 noel

noel

    Frequent Member

  • Advanced user
  • 137 posts
  • Location:nantes
  •  
    France

Posted 15 April 2020 - 12:39 PM

I don't have such devices. I have in hand a small BTH speaker and my smartphone.
I've read about BTH LE but I'm far from understanding everything. Having no BTH LE device I didn't look on the WEB if there were examples of code to do the coupling.
Sorry.
If you're on your side thinking of how to do this, be nice to tell me.
Thank you.

...

I did a quick search on the WEB. And I couldn't find anything for conventional APIs. A ability to do like a hook by displaying its "custom Device Pairing UI" for a UWP application: https://github.com/m...ationAndPairing






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users