Topic: Check Target System Files  (Read 5216 times)

Re: Check Target System Files
« Reply #40 on: March 24, 2019, 01:27:51 AM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Very Nice Muggles..
 :thumbup:

Re: Check Target System Files
« Reply #41 on: March 24, 2019, 02:16:23 AM »

slore

  • WimBuilder
  • Sr. Chef
  • ****
  • Date Registered: Jun 2016
  • Posts: 664
Quote
Switch to Admin mode never did switch and left me with a black screen and a cursor with an hourglass

the new mun files is just the first step for supporting 19H1.

Not only SwitchtoAdmin, WOW64, IE, IME are also unfunctional with current WIN10XPE.

As WimBuilderUI's RE:WIN10XPE already done with them, share for here to save our time to do something new/fix known issues & improve project than do same things.

commit 2673178f Support Windows 10 19H1 source
Projects/WIN10XPE/00-Configures/Build/WoW64_Basic/submain.bat
Quote
@windows\SysWOW64\
C_*.NLS,KBD*.dll

+ver > 18300
umpdc.dll
+ver*

commit fdcec843 fix issue that 19H1,20H1 can't switch to Administrator account.(yamingw)
Projects/WIN10XPE/00-Configures/System/Admin/SwitchToAdmin.bat
Quote
+ver > 17700
Windows.UI.Xaml.Controls.dll,Windows.ApplicationModel.dll

+ver > 18300
wuceffects.dll
+ver*


commit 13bc0470 update 19h1 support
Projects/WIN10XPE/00-Configures/System/Admin/SwitchToAdmin.bat
Quote
rem add all as default
set VER_CNAME=.*.
if %VER[3]% GTR 17000 set VER_CNAME=.rs4.
if %VER[3]% GTR 17700 set VER_CNAME=.rs5.
if %VER[3]% GTR 18300 set VER_CNAME=.19h1.

@\Windows\System32\

; 1709 uses Xaml.Resources.dll,1803 uses Xaml.Resources.rs4.dll and 1809 uses Xaml.Resources.rs5.dll, ...
; Keep both for compatibility with both versions
;Windows.UI.Xaml.Resources.dll,Windows.UI.Xaml.Resources.*.dll

Windows.UI.Xaml.Resources%VER_CNAME%dll

Projects/WIN10XPE/01-Components/IME/Ime_Common.bat

Quote
+ver > 18300
umpdc.dll
clbcatq.dll,dusmapi.dll
netprofm.dll,npmproxy.dll
Windows.Networking.HostName.dll
TextInputMethodFormatter.dll,WordBreakers.dll
+ver*


:Ime_Reg
if %VER[3]% GTR 18300 (
  call RegCopy %1\Microsoft\FuzzyDS
)


Projects/WIN10XPE/02-Apps/Browsers/IE/main.bat
Quote
+ver > 18300
DXCore.dll
*ver


commit 24fd326a fix issue that 19H1,20H1 can't use IME.(yamingw)
 Projects/WIN10XPE/01-Components/IME/Ime_Common.bat
Quote
TextInputMethodFormatter.dll,WordBreakers.dll
Language*.dll
Windows.UI.Core.TextInput.dll

+ver*


commit 1446ea0e update New Browse Dialog for the latest 19H1,20H1(JFX)
Projects/WIN10XPE/01-Components/00-Shell/Explorer/submain.bat
Quote
+ver <= 17700 or (ver > 18334 and ver < 18800) or ver > 18836
shellstyle.dll
en-US\shellstyle.dll.mui
; remove ver check (add with any ver)
+ver*


 :tongue: maybe this is off of the topic, if somebody want me to move this, just PM me.
« Last Edit: March 24, 2019, 02:46:26 AM by slore »

Re: Check Target System Files
« Reply #42 on: March 24, 2019, 09:49:32 AM »

ChrisR

  • Moderator, XPE Baker
  • Grand Chef
  • *****
  • Date Registered: Mar 2011
  • Posts: 3494
Both the x86 and x64 19H1 tests went great and I was able to open every program I tried, see desktop.
Thanks muggles for these tests with the latest Insider  :thumbsup: 
Nice screenshot, it's great to see that all these apps work. It's a thank-you to James :great:

Re: Check Target System Files
« Reply #43 on: March 24, 2019, 09:52:45 AM »

ChrisR

  • Moderator, XPE Baker
  • Grand Chef
  • *****
  • Date Registered: Mar 2011
  • Posts: 3494
the new mun files is just the first step for supporting 19H1.
Thanks for your list of changes  :thumbsup:
it will be helpful
It's just a beta in dev but already quite advanced.

However, many of the dependencies have already been added in addition to the new mun files
shellstyle.dll of course
DXCore.dll and umpdc.dll already in winre.wim, I also added in WoW64
Windows.UI.Xaml.Controls.dll,Windows.ApplicationModel.dll already here for 17763
Windows.UI.Xaml.Resources.19h1.dll

For C_*.NLS, KBD*.dll in SysWoW64, I haven't seen the need to add them yet, IE11 is x64 only
Probably other Applications need and I don't know if it's good to add in Basic

Otherwise in relation to beta:
I haven't tested Admin yet.
IME I am not really able to check so thanks for the new dependencies
To do, I also noted the reduced list of catalogues (*.cat) to check
The rest needs more testing but seems already not to bad  :wink:

Re: Check Target System Files
« Reply #44 on: March 24, 2019, 10:23:36 AM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Quote
it's great to see that all these apps work. It's a thank-you to James
Credit to Muggles, as Most of those are Muggles Apps..

Re: Check Target System Files
« Reply #45 on: March 24, 2019, 11:20:36 AM »

ChrisR

  • Moderator, XPE Baker
  • Grand Chef
  • *****
  • Date Registered: Mar 2011
  • Posts: 3494
Yes, indeed :thumbsup:
Thanks to Muggles, that's a great job but thanks to you too, also. A collaborative work, I like :thumbsup:

Re: Check Target System Files
« Reply #46 on: March 24, 2019, 12:15:04 PM »

muggles

  • Jr. Chef
  • **
  • Date Registered: Mar 2013
  • Posts: 50
A collaborative work, I like :thumbsup:

Credits=*PE*  :great:

Re: Check Target System Files
« Reply #47 on: March 24, 2019, 12:37:28 PM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Credits = TheOven.org Forum
We all know who contributes to *PE* here...

Re: Check Target System Files
« Reply #48 on: March 25, 2019, 03:33:21 PM »

cretino

  • Chef
  • ***
  • Date Registered: Jan 2018
  • Posts: 240
hi ChrisR

tested Win10XPE_2019-03-23 with this parametre
ila_rendered
everything work ok   :smile:
but
if i add Microsoft .NETFx4 , i have error " native filter error,
same thing if i add Network Additions ( also same thing with both added )
(like in muggles's screenshot -bottom right- )
...

Re: Check Target System Files
« Reply #49 on: March 27, 2019, 12:03:40 AM »

cretino

  • Chef
  • ***
  • Date Registered: Jan 2018
  • Posts: 240
hi ChrisR
i find the way to integrate the theme  :smile:
while Browse SystemResources folder to see why my animated cursor not work i see a folder and i make test whit it to see & Switch to Administrator work  :grin:
ila_rendered

it is Windows.UI.Logon folder

Re: Check Target System Files
« Reply #50 on: March 29, 2019, 06:30:54 PM »

ChrisR

  • Moderator, XPE Baker
  • Grand Chef
  • *****
  • Date Registered: Mar 2011
  • Posts: 3494
Thanks for your feedback cretino :thumbsup:
I also had seen about Windows.UI.Logon, thanks to muggles  :thumbsup:
As a test, 17763 gave the same bad results with the new code so that may say something.

I had deleted by mistake during the cleaning (mui, mun files) done too quickly  :embarrassed:
Code: [Select]
\Windows\SystemResources\Windows.UI.Logon

Thanks also to slore for wuceffects.dll  :thumbsup:
+ver > 18300
wuceffects.dll
+ver*


if i add Microsoft .NETFx4 , i have error " native filter error,
I also noticed for Wlansvc, it does not start indeed with the full Software (used if DotNet or Admin selected) and with Network Additions
I wasn't at home this week but I did few tests and I think I saw why but I need more tests now.
« Last Edit: March 29, 2019, 06:33:41 PM by ChrisR »

Re: Check Target System Files
« Reply #51 on: March 29, 2019, 09:29:06 PM »

cretino

  • Chef
  • ***
  • Date Registered: Jan 2018
  • Posts: 240
hi ChrisR

Quote
Thanks also to slore for wuceffects.dll  :thumbsup:
this one was added by RemoteDesktop_XPE.script, i make a test without it and Switch to Administrator didnt work... (even with  Windows.UI.Logon folder)

this what i made for my build,I am not a master of codes like you ,I can not differentiate which of the system or not...,if you can sort them ...

Custom Theme
Code: [Select]
[Registry]
RegWrite,HKLM,0x1,Tmp_Software\Classes\.ani,,anifile
RegWrite,HKLM,0x1,Tmp_Software\Classes\anifile,,"Animated Cursor"
RegWrite,HKLM,0x2,Tmp_Software\Classes\anifile,FriendlyTypeName,"@#$pSystemRoot#$p\system32\main.cpl,-2000"
RegWrite,HKLM,0x1,Tmp_Software\Classes\anifile\DefaultIcon,,#$p1
//
RegWrite,HKLM,0x1,Tmp_Software\Classes\.deskthemepack,,desktopthemepackfile
RegWrite,HKLM,0x1,Tmp_Software\Classes\desktopthemepackfile,,"Windows Desktop Theme Pack"
RegWrite,HKLM,0x1,Tmp_Software\Classes\desktopthemepackfile,FriendlyTypeName,"@themeui.dll,-2695"
RegWrite,HKLM,0x2,Tmp_Software\Classes\desktopthemepackfile\DefaultIcon,,"#$pSystemRoot#$p\system32\themeui.dll,-704"
RegWrite,HKLM,0x2,Tmp_Software\Classes\desktopthemepackfile\shell\open\command,,"#$pSystemRoot#$p\system32\rundll32.exe #$pSystemRoot#$p\system32\themecpl.dll,OpenThemeAction #$p1"
//
RegWrite,HKLM,0x1,Tmp_Software\Classes\.msstyles,,msstylesfile
RegWrite,HKLM,0x1,Tmp_Software\Classes\msstylesfile,,"Windows Visual Style File"
RegWrite,HKLM,0x1,Tmp_Software\Classes\msstylesfile,FriendlyTypeName,"@themeui.dll,-2684"
RegWrite,HKLM,0x2,Tmp_Software\Classes\msstylesfile\DefaultIcon,,"#$pSystemRoot#$p\system32\themeui.dll,-701"
RegWrite,HKLM,0x2,Tmp_Software\Classes\msstylesfile\shell\open\command,,"#$pSystemRoot#$p\system32\rundll32.exe #$pSystemRoot#$p\system32\shell32.dll,Control_RunDLL #$pSystemRoot#$p\system32\desk.cpl desk,@Appearance /Action:OpenMSTheme /file:#$q#$p1#$q"
//
RegWrite,HKLM,0x1,Tmp_Software\Classes\.theme,,themefile
RegWrite,HKLM,0x1,Tmp_Software\Classes\themefile,,"Windows Theme File"
RegWrite,HKLM,0x1,Tmp_Software\Classes\themefile,FriendlyTypeName,"@themeui.dll,-2683"
RegWrite,HKLM,0x4,Tmp_Software\Classes\themefile,Treatment,0
RegWrite,HKLM,0x1,Tmp_Software\Classes\themefile,TypeOverlay,
RegWrite,HKLM,0x2,Tmp_Software\Classes\themefile\DefaultIcon,,"#$pSystemRoot#$p\system32\themeui.dll,-701"
RegWrite,HKLM,0x2,Tmp_Software\Classes\themefile\shell\open\command,,"#$pSystemRoot#$p\system32\rundll32.exe #$pSystemRoot#$p\system32\themecpl.dll,OpenThemeAction #$p1"
RegWrite,HKLM,0x1,Tmp_Software\Classes\themefile\shellex\{E357FCCD-A995-4576-B01F-234630154E96},,{49C407EF-78B9-4C82-A40B-2FE02F8E771D}
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-themefile-aero_31bf3856ad364e35_none_5fdc25f62b1be713,,10.0
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-themefile-aero_31bf3856ad364e35_none_5fdc25f62b1be713\10.0,10.0.18361.1,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-themefile-aero_31bf3856ad364e35_none_5fdc25f62b1be713\10.0,,10.0.18361.1
//
RegWrite,HKLM,0x4,Tmp_Default\Software\Microsoft\Windows\CurrentVersion\ApplicationAssociationToasts,themefile_.theme,0
RegWrite,HKLM,0x1,Tmp_Default\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.theme\OpenWithProgids,themefile,
//
RegWrite,HKLM,0x1,Tmp_Software\Classes\.themepack,,themepackfile
RegWrite,HKLM,0x1,Tmp_Software\Classes\themepackfile,,"Windows Theme Pack"
RegWrite,HKLM,0x1,Tmp_Software\Classes\themepackfile,FriendlyTypeName,"@themeui.dll,-2685"
RegWrite,HKLM,0x2,Tmp_Software\Classes\themepackfile\DefaultIcon,,"#$pSystemRoot#$p\system32\themeui.dll,-704"
RegWrite,HKLM,0x2,Tmp_Software\Classes\themepackfile\shell\open\command,,"#$pSystemRoot#$p\system32\rundll32.exe #$pSystemRoot#$p\system32\themecpl.dll,OpenThemeAction #$p1"
//
RegWrite,HKLM,0x1,Tmp_Software\Classes\Theme.Manager,,"Windows Theme Manager API"
RegWrite,HKLM,0x1,Tmp_Software\Classes\Theme.Manager\CLSID,,{2E17C0EF-2851-459b-A3C8-27A41D4BC9F7}
RegWrite,HKLM,0x1,Tmp_Software\Classes\Theme.Manager\CurVer,,Theme.Manager.1
RegWrite,HKLM,0x1,Tmp_Software\Classes\Theme.ThemeThumbnail,,"Windows Theme Thumbnail Preview"
RegWrite,HKLM,0x1,Tmp_Software\Classes\Theme.ThemeThumbnail\CLSID,,{49C407EF-78B9-4C82-A40B-2FE02F8E771D}
RegWrite,HKLM,0x1,Tmp_Software\Classes\Theme.ThemeThumbnail\CurVer,,Theme.ThemeThumbnail.1
RegWrite,HKLM,0x1,Tmp_Software\Classes\Theme.ThemeThumbnail.1,,"Windows Theme Thumbnail Preview"
RegWrite,HKLM,0x1,Tmp_Software\Classes\Theme.ThemeThumbnail.1\CLSID,,{49C407EF-78B9-4C82-A40B-2FE02F8E771D}
//
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\Active Setup\Installed Components\{2C7339CF-2B09-4501-B3F3-F3508C9228ED}",,"Themes Setup"
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\Active Setup\Installed Components\{2C7339CF-2B09-4501-B3F3-F3508C9228ED}",ComponentID,"Theme Component"
RegWrite,HKLM,0x4,"Tmp_Software\Microsoft\Active Setup\Installed Components\{2C7339CF-2B09-4501-B3F3-F3508C9228ED}",Enabled,1
RegWrite,HKLM,0x4,"Tmp_Software\Microsoft\Active Setup\Installed Components\{2C7339CF-2B09-4501-B3F3-F3508C9228ED}",IsInstalled,1
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\Active Setup\Installed Components\{2C7339CF-2B09-4501-B3F3-F3508C9228ED}",Locale,EN
RegWrite,HKLM,0x2,"Tmp_Software\Microsoft\Active Setup\Installed Components\{2C7339CF-2B09-4501-B3F3-F3508C9228ED}",LocalizedName,"@#$pSystemRoot#$p\system32\themeui.dll,-2682"
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\Active Setup\Installed Components\{2C7339CF-2B09-4501-B3F3-F3508C9228ED}",ShellComponent,themeui.dll
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\Active Setup\Installed Components\{2C7339CF-2B09-4501-B3F3-F3508C9228ED}",StubPath,/UserInstall
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\Active Setup\Installed Components\{2C7339CF-2B09-4501-B3F3-F3508C9228ED}",Version,"1,1,1,9"
//
RegWrite,HKLM,0x2,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{531a35ab-63ce-4bcf-aa98-f88c7a89e455},ResourceFileName,#$pSystemRoot#$p\system32\Windows.UI.Xaml.dll
RegWrite,HKLM,0x2,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{531a35ab-63ce-4bcf-aa98-f88c7a89e455},MessageFileName,#$pSystemRoot#$p\system32\Windows.UI.Xaml.dll
RegWrite,HKLM,0x2,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{59e7a714-73a4-4147-b47e-0957048c75c4},ResourceFileName,#$pSystemRoot#$p\system32\Windows.UI.Xaml.dll
RegWrite,HKLM,0x2,Tmp_Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{59e7a714-73a4-4147-b47e-0957048c75c4},MessageFileName,#$pSystemRoot#$p\system32\Windows.UI.Xaml.dll
//
RegWrite,HKLM,0x2,Tmp_Software\Classes\CLSID\{c04b329e-5823-4415-9c93-ba44688947b0}\InProcServer32,,#$pSystemRoot#$p\system32\themeui.dll
RegWrite,HKLM,0x1,Tmp_Software\Classes\CLSID\{c04b329e-5823-4415-9c93-ba44688947b0}\InProcServer32,ThreadingModel,Apartment

[AddFiles]
\Windows\System32\themecpl.dll
\Windows\System32\??-??\themecpl.dll.mui
\Windows\SystemResources\themecpl.dll.mun
\Windows\System32\Windows.UI.Xaml.dll
\Windows\System32\??-??\Windows.UI.Xaml.dll.mui

Optimizations 1903 18361.1
Code: [Select]
[ProcessM_AddFiles]
\Windows\System32\??-??\imagesp1.dll.mui
\Windows\SystemResources\imagesp1.dll.mun
\Windows\System32\wcmapi.dll
\Windows\System32\cldapi.dll
\Windows\System32\amsi.dll
\Windows\System32\??-??\shell32.dll.mui
\windows\SystemResources\USER32.dll.mun
\Windows\System32\Windows.UI.AppDefaults.dll
\Windows\System32\resourcepolicyclient.dll

[Win10XPE_AddFiles]
\Windows\SystemResources\Taskmgr.exe.mun

[admin_AddFiles]
\Windows\SystemResources\Windows.UI.Logon

[sib_AddFiles]
\Windows\System32\sud.dll
\Windows\System32\??-??\sud.dll.mui
\Windows\SystemResources\sud.dll.mun
\Windows\SystemResources\GdiPlus.dll.mun
\Windows\System32\wuaueng.dll
\Windows\System32\??-??\wuaueng.dll.mui
\Windows\System32\ngcrecovery.dll
\Windows\System32\??-??\ngcrecovery.dll.mui

[Explorer_AddFiles]
\Windows\System32\??-??\main.cpl.mui
\Windows\SystemResources\main.cpl.mun

[theme_AddFiles]
\Windows\System32\usercpl.dll
\Windows\System32\??-??\usercpl.dll.mui
\Windows\SystemResources\usercpl.dll.mun


Re: Check Target System Files
« Reply #52 on: March 30, 2019, 02:09:12 AM »

slore

  • WimBuilder
  • Sr. Chef
  • ****
  • Date Registered: Jun 2016
  • Posts: 664
I also noticed for Wlansvc, it does not start indeed with the full Software (used if DotNet or Admin selected) and with Network Additions

commit 982e7c22 remove WcmSvc from Wlansvc service's DependOnService

Maybe this? I don't test with network.

Re: Check Target System Files
« Reply #53 on: March 30, 2019, 02:26:39 AM »

ChrisR

  • Moderator, XPE Baker
  • Grand Chef
  • *****
  • Date Registered: Mar 2011
  • Posts: 3494
commit 982e7c22 remove WcmSvc from Wlansvc service's DependOnService
Yes, it is wcmsvc which does not start and so wlansvc too
However, I think I found, The netprofm service, not written as dependency, seems necessary.

I need more testing but it looks good with only the netprofm registry services even disabled, Start=4 and without files dependencies.
Code: [Select]
RegCopyKey,HKLM,Tmp_System\ControlSet001\Services\netprofm
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\netprofm,Start,4

Re: Check Target System Files
« Reply #54 on: March 30, 2019, 02:52:07 AM »

ChrisR

  • Moderator, XPE Baker
  • Grand Chef
  • *****
  • Date Registered: Mar 2011
  • Posts: 3494
I just tested on my real machine with Switch to Admin, DotNET and Network Additions.
I confirm that it looks good with the netprofm service even disabled  :thumbsup:

Re: Check Target System Files
« Reply #55 on: March 30, 2019, 04:06:44 AM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Win10XPE_2019-03-14 Release > Build Core Error > Build 18343 x64 & x86

Error: Wimlib Extract shellstyle.dll from Install.wim Return: 49 - File Not Found

Found:
\Windows\Resources\Themes\aero\Shell\NormalColor\en-US\shellstyle.dll.mui
\Windows\WinSxS\amd64_microsoft-windows-aero_ss.resources_31bf3856ad364e35_10.0.18343.1_en-us_1044584429f1cf78\shellstyle.dll.mui
\Windows\Resources\Themes\aero\Shell\NormalColor\shellstyle.dll
\Windows\WinSxS\amd64_microsoft-windows-aero_ss_31bf3856ad364e35_10.0.18343.1_none_de8c6683bd0e27a9\shellstyle.dll

Re: Check Target System Files
« Reply #56 on: March 30, 2019, 04:11:14 AM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Also Testing MS Edge with 18343 x64

Most likely without Admin, NetFx4

Got Popup question box to Start a Network Service > Yes
Went through PENetwork Profile / AutoConnect
Closed - but no tray icon

Internet worked...

Just a network report from my testing yesterday..

Re: Check Target System Files
« Reply #57 on: March 30, 2019, 10:30:17 AM »

ChrisR

  • Moderator, XPE Baker
  • Grand Chef
  • *****
  • Date Registered: Mar 2011
  • Posts: 3494
I just arrived and I'm already leaving again, for WE only.

I don't know about the error 49, File Not Found.
I don't get it with 18362. shellstyle.dll should be there. Written in explorer.script
Code: [Select]
\Windows\Resources\Themes\aero\Shell\NormalColor

I haven't tested Ms. Edge yet. I'll try to stay focused on 1903 for now.
I'll test later when I have more time

Re: Check Target System Files
« Reply #58 on: March 30, 2019, 10:38:45 AM »

ChrisR

  • Moderator, XPE Baker
  • Grand Chef
  • *****
  • Date Registered: Mar 2011
  • Posts: 3494
commit 982e7c22 remove WcmSvc from Wlansvc service's DependOnService

Maybe this? I don't test with network.
With Network additions, I will add the netprofm service with start=4 disabled

But yes it's worth a try with the full software hive and without network additions
and to remove wcmsvc as a wlansvc dependency.
It is fine if it works like that.
Without the need for "network additions" dependency for DotNEt and Admin (they use the full Software)

Re: Check Target System Files
« Reply #59 on: March 30, 2019, 01:40:11 PM »

James

  • Grand Chef
  • *****
  • Location: USA
  • Date Registered: Dec 2017
  • Posts: 2272
Quote
I don't get it with 18362. shellstyle.dll should be there. Written in explorer.script
We not on same page here... as I do not have in explorer.script - 2019.03.06


 

Powered by EzPortal