Windows 10 19H2 1909 18363 END for iPack users

[றѳѳղղįqվદ®]

Hello my dear Friends
Windows 10 October update 19H2 1909 18363

All files has now been moved from c/windows/system32
and from c/windows/syswow64 directory
for example imageres.dll

Windows 10 19H2 1909 18363
now using only the new specific directory
c./Windows/SystemResources

with new .mun files Unsupported for iPack
and thats really big problem for iPack and for iPack Lovers
my Personal Recommendation is stopping using iPack
if you are on Windows 10 19H2 1909 18363
or just stay on Windows 10 19H1 1903 18362
all of the new files need now saving as imageres.dll.mun.res etc
and all of the new .mun files can be Patched only with new 7tsp
Se7en Theme Source Patcher v0.6 2019
by [Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]

Information

All files has now been moved from c/windows/system32 and from c/windows/SysWOW64 directory now not need to patching this both directories just save all files as .mun 19H2 now not supported saved files as imageres.dll.res shell32.dll.mui.res all of the new files need to save as (example) imageres.dll.mun.res shell32.dll.mun.res not as shell32.dll.mui.res

WARNING

Windows 7 explorer.exe need to save as explorer.exe.res imageres.dll need to save as imageres.dll.res imagesp1.dll need to save as imagesp1.dll.res shell32.dll need to save as shell32.dll.res Windows 8 8.1 and Windows 10 TH2-RS5 explorer.exe need to save as explorer.exe.mui.res imageres.dll need to save as imageres.dll.res imagesp1.dll need to save as imagesp1.dll.res shell32.dll need to save as shell32.dll.mui.res Windows 10 1903 19h1 , 1909 19h2 and 20h1 explorer.exe need to save as explorer.exe.mui.res imageres.dll need to save as imageres.dll.mun.res imagesp1.dll need to save as imagesp1.dll.mun.res shell32.dll need to save as shell32.dll.mun.res notepad.exe need to save as notepad.exe.mun.res themecpl.dll need to save as themecpl.dll.mun.res zipfldr.dll need to save as zipfldr.dll.mun.res

[Nimbi]

i think no only iPack and yes if you need 7tsp you need extract iPack
then delete all unsupported files for w10 and if you are on w10 19h1+
you need create or port all to the mew .mun files
original iPack here
[Only registered and activated users can see links. ]

Yo, interesting discovery, but it seems there are some systems that don't appear to need that new mun files. I'm running Windows 10 1909 and the magnum iPack still works for me...

[Only registered and activated users can see links. ]

Mainly tested because I noticed my system was still appearing to load it's icons from the dlls and I got curious to see if it would work.... and welp... I'm pleasently surprised xD
So, it seems not all systems have adopted the mun file requirement.

[றѳѳղղįqվદ®]

Yo, interesting discovery, but it seems there are some systems that don't appear to need that new mun files. I'm running Windows 10 1909 and the magnum iPack still works for me...

[Only registered and activated users can see links. ]


Mainly tested because I noticed my system was still appearing to load it's icons from the dlls and I got curious to see if it would work.... and welp... I'm pleasently surprised xD
So, it seems not all systems have adopted the mun file requirement.

because iPack create a fake file in your system32 direcrtory
w10 19h1 and 19h2 not using system32 and syswow64 directory for imageres
in 19h1 and 19h2 has been moved to SystemResources
sorry but i am creating and replacing system files 9years and creating a fake files in system directories can have adverse avoid for windows
the same as for shell32.dll = this break down your system
therefore I do not recommend using iPack but 7tsp tested by me and updated with support for patching the original new .mun files by Microsoft
[Only registered and activated users can see links. ]

[Nimbi]

because iPack create a fake file in your system32 direcrtory
w10 19h1 and 19h2 not using system32 and syswow64 directory for imageres
in 19h1 and 19h2 has been moved to SystemResources
sorry but i am creating and replacing system files 9years and creating a fake files in system directories can have adverse avoid for windows
the same as for shell32.dll = this break down your system
therefore I do not recommend using iPack but 7tsp tested by me and updated with support for patching the original new .mun files by Microsoft
[Only registered and activated users can see links. ]

ah ok. I assumed mine simply hadn't changd any since I've noticed i still have all of my icons in the dll files even without using the iPack xD. My bad xD

[றѳѳղղįqվદ®]

Yo, interesting discovery, but it seems there are some systems that don't appear to need that new mun files. I'm running Windows 10 1909 and the magnum iPack still works for me...

[Only registered and activated users can see links. ]


Mainly tested because I noticed my system was still appearing to load it's icons from the dlls and I got curious to see if it would work.... and welp... I'm pleasently surprised xD
So, it seems not all systems have adopted the mun file requirement.

because iPack create a fake file in your system32 direcrtory
w10 19h1 and 19h2 not using system32 and syswow64 directory for imageres
in 19h1 and 19h2 has been moved to SystemResources
sorry but i am creating and replacing system files 9years and creating a fake files in system directories can have adverse avoid for windows
the same as for shell32.dll = this break down your system
therefore I do not recommend using iPack but 7tsp tested by me and updated with support for patching the original new .mun files by Microsoft
[Only registered and activated users can see links. ]

ah ok. I assumed mine simply hadn't changd any since I've noticed i still have all of my icons in the dll files even without using the iPack xD. My bad xD

Hope if this help
this posts has been copied here and sorry friends because i dont have more free time for updating all of my threads
for better understanding i am creating , testing and patching system files 9years
and here some info where is the real problem with using iPack
iPack not Supported on w10 19h1 1903 18362 and w10 1909 18363
because all files from original System32 and SysWOW64 directory are moved to SystemResources directory
if you create many .res files in your iPack and patching your system iPack create a Fake files in your System directory
if you patching only imageres.dll its all ok but if you create more Fake iPack files
after patching you make changes to your system files and this can lead to unexpected problems
or total breakdown of Windows! black screen after next reboot .etc
for better understanding 2 images here where is the real problem
Image 1 System32 = blank directory
Image 2 SystemResources

and here ome image from my iPacks

and my official Announcement