PDA

View Full Version : Windows 10 19H1/19H2 1903/1909 18362/18363 END for iPack users



ミறѳѳղղįզվદ彡
September 29th, 2019, 12:33 PM
Windows 10 19H1/19H2 1903/1909 18362/18363
END for iPack users
:sad:
Hello my dear Friends
Windows 10 October update 19H2 1909 18363
85708
All files has now been moved from c/windows/system32
and from c/windows/syswow64 directory
for example imageres.dll
84386
Windows 10 19H2 1909 18363
now using only the new specific directory
c./Windows/SystemResources
84387
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 Fixit (https://virtualcustoms.net/member.php/159280-Fixit)
https://virtualcustoms.net/TOOL-Se7en-Theme-Source-patcher-v0-6-Build-2019 (https://virtualcustoms.net/showthread.php/83629-TOOL-Se7en-Theme-Source-patcher-v0-6-Build-2019)
84385
84389

84422
84423
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
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

devillnside
September 30th, 2019, 01:00 AM
thanks a lot for the info moon!! but either way, ever since the new 7TSP was released, ipacks lost its appeal to me as not only can 7tsp patch better it can apply icons to parts ipack could never touch on windows 10

ミறѳѳղղįզվદ彡
September 30th, 2019, 02:31 PM
thanks a lot for the info moon!! but either way, ever since the new 7TSP was released, ipacks lost its appeal to me as not only can 7tsp patch better it can apply icons to parts ipack could never touch on windows 10




yes yes i agree and i am using 7tsp 10 years without any problems because only 7tsp can patching more special system files
but many peoples dont know other special funkcions of 7tsp
you can add start orb or wallaper custom theme or cursors and sounds



DeviantArt
but i wonder whether these changes will affect the ability to use 3rd party themes on 19H2

and this 19H2 changes dont have affects for using 3rd party themes
working good start is back , old new explorer 1.1.8.4 and 1.1.9 and UltraUXTheme patcher 3.6.2
because all of the 19H1 1903 themes working great on 19H2 1909 without any problems or updating shellstyle or scripts:peace:

devillnside
October 1st, 2019, 01:50 AM
yes yes i agree and i am using 7tsp 10 years without any problems because only 7tsp can patching more special system files
but many peoples dont know other special funkcions of 7tsp
you can add start orb or wallaper custom theme or cursors and sounds




and this 19H2 changes dont have affects for using 3rd party themes
working good start is back , old new explorer 1.1.8.4 and 1.1.9 and UltraUXTheme patcher 3.6.2
because all of the 19H1 1903 themes working great on 19H2 1909 without any problems or updating shellstyle or scripts:peace:

cool!!! good to know!!

ミறѳѳղղįզվદ彡
October 7th, 2019, 09:58 AM
84426
84427

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

STEFANOCOLLARINI12
October 27th, 2019, 07:19 AM
thanks you a lot of mind

ミறѳѳղղįզվદ彡
October 27th, 2019, 07:05 PM
thanks you a lot of mind
:girl:

Stankfiss
November 15th, 2019, 04:08 AM
Only issue with me is i get this error using 7tsp. 7tsp is for windows seven. :crying:

Grim Reaper
November 15th, 2019, 01:07 PM
i'll add one thing and that is a lot of the sites are suggesting with this to ditch all the old 10's and do a fresh install of this. i'm assuming it has to do with the changes to various files and their locations. that said i'll be working on my roommates system and would like a list of the theme tweaking apps that are currently compatible with 1909 and their version numbers. thanks

Grim Reaper
November 16th, 2019, 12:12 PM
i'll add one thing and that is a lot of the sites are suggesting with this to ditch all the old 10's and do a fresh install of this. i'm assuming it has to do with the changes to various files and their locations. that said i'll be working on my roommates system and would like a list of the theme tweaking apps that are currently compatible with 1909 and their version numbers. thanks

BUMP!

Donkuz
November 16th, 2019, 12:44 PM
Gday Mate, Sorry I didnt see this earlier, so 1909 is catching up with everyone, me to. Any way heres the Dirt on W10 1909.
all the old Mods still work on this and the themes for 1903 just make sure your in Default W10 theme before you try updating.After the update all your old Mods should all still be Installed
Im running it myself and have all the most up to date Mods, here's a screen shot of my apps so you can see what Im using.84690
You also need OldNewExplorer Still too.
I hope this helps you out, let me know how ya go Bro:peace:Cheerz!!

ミறѳѳղղįզվદ彡
November 16th, 2019, 12:59 PM
19h2 is only the feature update and no major update
w10 19h1 1903 working on the same base as w10 19h2 1909
all themes from 19h1 and all other extras working great on 19h2
OldNewExplorer Start is back 7tsp and all other .dll .mun .mui .res
Windows 10 19h2 OS build 1909 18363 working on 18362 base
84691

Nimbi
November 18th, 2019, 05:38 PM
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
https://virtualcustoms.net/showthread.php/70312-Magnum-Full-System-manual-Install-Icon-pack (https://virtualcustoms.net/showthread.php/70312-Magnum-Full-System-manual-Install-Icon-pack)

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...


84727


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.

ミறѳѳղղįզվદ彡
November 18th, 2019, 05:50 PM
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...

84727


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
84729

Nimbi
November 18th, 2019, 06:04 PM
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
84729

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

ミறѳѳղղįզվદ彡
November 19th, 2019, 02:04 PM
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...

84727


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
84729



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
84735
and here ome image from my iPacks
84736
and my official Announcement
84737

ミறѳѳղղįզվદ彡
December 15th, 2019, 08:17 PM
Windows 10 19h1 1903 18362
Windows 10 19h2 1909 18363
How to replace taskmgr.exe icon
84940
Windows 10 19h1+ are using the new .mun files
Remember all of the new .mun files can be patched only with new 7tsp GUI 2019
1.go to c/Windows/SystemResources and open file taskmgr.exe.mun with Restorator
2.replace icon number 107 and 30651
3.save taskmgr.exe.mun as taskmgr.exe.mun.res
4.patch your system with 7tsp GUI 2019
http://virtualcustoms.net/attachment.php?attachmentid=47413&d=1316585287
84938
http://virtualcustoms.net/attachment.php?attachmentid=47413&d=1316585287
84939
http://virtualcustoms.net/attachment.php?attachmentid=47413&d=1316585287
84940
http://virtualcustoms.net/attachment.php?attachmentid=48512&d=1318717506

ミறѳѳղղįզվદ彡
December 20th, 2019, 07:13 PM
Windows 10 19h1 1903 18362 and Windows 10 19h2 1909 18363
now is patching more secured as on the older Windows 10 TH2-RS5 builds
after creating a new packs and testing 7tsp 6 months every day
7tsp 2019 and replacing new .mun files in the SystemResources directory is more secured
as replacing icons .dll .exe and .mui files .etc in the System32 and SysWOW64 directory
https://virtualcustoms.net/attachment.php?attachmentid=84484&d=1571046870
https://virtualcustoms.net/TOOL-Se7en-Theme-Source-patcher-v0-6-Build-2019 (https://virtualcustoms.net/showthread.php/83629-TOOL-Se7en-Theme-Source-patcher-v0-6-Build-2019)
you can replace any of the .mun file what you like in the SystemResources directory
without any problem and unexcepted crashing after patching or next reboot

ミறѳѳղղįզվદ彡
January 13th, 2020, 10:18 PM
Complete list of .mun files in Windows 10 1903 19h1 19h2 20h1 and 20h2

\Windows\SystemResources\accessibilitycpl.dll.mun
\Windows\SystemResources\aclui.dll.mun
\Windows\SystemResources\ActionCenterCPL.dll.mun
\Windows\SystemResources\appwiz.cpl.mun
\Windows\SystemResources\AuthFWGP.dll.mun
\Windows\SystemResources\authui.dll.mun
\Windows\SystemResources\azroles.dll.mun
\Windows\SystemResources\batmeter.dll.mun
\Windows\SystemResources\BingMaps.dll.mun
\Windows\SystemResources\certCredProvider.dll.mun
\Windows\SystemResources\Chakra.dll.mun
\Windows\SystemResources\cleanmgr.exe.mun
\Windows\SystemResources\colorui.dll.mun
\Windows\SystemResources\comdlg32.dll.mun
\Windows\SystemResources\compstui.dll.mun
\Windows\SystemResources\comres.dll.mun
\Windows\SystemResources\connect.dll.mun
\Windows\SystemResources\crypt32.dll.mun
\Windows\SystemResources\cryptui.dll.mun
\Windows\SystemResources\cryptuiwizard.dll.mun
\Windows\SystemResources\cttune.exe.mun
\Windows\SystemResources\DataExchange.dll.mun
\Windows\SystemResources\dccw.exe.mun
\Windows\SystemResources\DDORes.dll.mun
\Windows\SystemResources\DeviceCenter.dll.mun
\Windows\SystemResources\DevicePairing.dll.mun
\Windows\SystemResources\DevicePairingFolder.dll.mun
\Windows\SystemResources\dfrgui.exe.mun
\Windows\SystemResources\dmdskres.dll.mun
\Windows\SystemResources\dsquery.dll.mun
\Windows\SystemResources\dsuiext.dll.mun
\Windows\SystemResources\dwmcore.dll.mun
\Windows\SystemResources\DxpTaskSync.dll.mun
\Windows\SystemResources\EaseOfAccessDialog.exe.mun
\Windows\SystemResources\edgehtml.dll.mun
\Windows\SystemResources\edputil.dll.mun
\Windows\SystemResources\ETWCoreUIComponentsResources.dll.mun
\Windows\SystemResources\ExplorerFrame.dll.mun
\Windows\SystemResources\fdprint.dll.mun
\Windows\SystemResources\filemgmt.dll.mun
\Windows\SystemResources\FirewallControlPanel.dll.mun
\Windows\SystemResources\gpedit.dll.mun
\Windows\SystemResources\icsigd.dll.mun
\Windows\SystemResources\ieapfltr.dll.mun
\Windows\SystemResources\ieframe.dll.mun
\Windows\SystemResources\imageres.dll.mun
\Windows\SystemResources\imagesp1.dll.mun
\Windows\SystemResources\inetcpl.cpl.mun
\Windows\SystemResources\intl.cpl.mun
\Windows\SystemResources\ipsecsnp.dll.mun
\Windows\SystemResources\iscsicli.exe.mun
\Windows\SystemResources\iscsicpl.dll.mun
\Windows\SystemResources\iscsicpl.exe.mun
\Windows\SystemResources\keymgr.dll.mun
\Windows\SystemResources\LaunchTM.exe.mun
\Windows\SystemResources\Magnify.exe.mun
\Windows\SystemResources\main.cpl.mun
\Windows\SystemResources\mdminst.dll.mun
\Windows\SystemResources\mfplat.dll.mun
\Windows\SystemResources\mmcbase.dll.mun
\Windows\SystemResources\mmcndmgr.dll.mun
\Windows\SystemResources\mmres.dll.mun
\Windows\SystemResources\mmsys.cpl.mun
\Windows\SystemResources\moricons.dll.mun
\Windows\SystemResources\msctf.dll.mun
\Windows\SystemResources\msdt.exe.mun
\Windows\SystemResources\mshtml.dll.mun
\Windows\SystemResources\mspaint.exe.mun
\Windows\SystemResources\mssvp.dll.mun
\Windows\SystemResources\mstask.dll.mun
\Windows\SystemResources\mstsc.exe.mun
\Windows\SystemResources\mstscax.dll.mun
\Windows\SystemResources\msutb.dll.mun
\Windows\SystemResources\msxml3.dll.mun
\Windows\SystemResources\mycomput.dll.mun
\Windows\SystemResources\mydocs.dll.mun
\Windows\SystemResources\netcenter.dll.mun
\Windows\SystemResources\netshell.dll.mun
\Windows\SystemResources\networkexplorer.dll.mun
\Windows\SystemResources\newdev.dll.mun
\Windows\SystemResources\notepad.exe.mun
\Windows\SystemResources\NPSMDesktopProvider.dll.mun
\Windows\SystemResources\ntshrui.dll.mun
\Windows\SystemResources\onexui.dll.mun
\Windows\SystemResources\PortableDeviceStatus.dll.mun
\Windows\SystemResources\powercpl.dll.mun
\Windows\SystemResources\printui.dll.mun
\Windows\SystemResources\prnfldr.dll.mun
\Windows\SystemResources\propsys.dll.mun
\Windows\SystemResources\psr.exe.mun
\Windows\SystemResources\qedwipes.dll.mun
\Windows\SystemResources\raschapext.dll.mun
\Windows\SystemResources\rasdlg.dll.mun
\Windows\SystemResources\rasgcw.dll.mun
\Windows\SystemResources\rasplap.dll.mun
\Windows\SystemResources\rastls.dll.mun
\Windows\SystemResources\rastlsext.dll.mun
\Windows\SystemResources\remotepg.dll.mun
\Windows\SystemResources\SearchIndexer.exe.mun
\Windows\SystemResources\SensorsCpl.dll.mun
\Windows\SystemResources\sethc.exe.mun
\Windows\SystemResources\shell32.dll.mun
\Windows\SystemResources\shrpubw.exe.mun
\Windows\SystemResources\shsvcs.dll.mun
\Windows\SystemResources\SndVolSSO.dll.mun
\Windows\SystemResources\sppcomapi.dll.mun
\Windows\SystemResources\srchadmin.dll.mun
\Windows\SystemResources\SrpUxNativeSnapIn.dll.mun
\Windows\SystemResources\stobject.dll.mun
\Windows\SystemResources\sud.dll.mun
\Windows\SystemResources\SyncCenter.dll.mun
\Windows\SystemResources\sysdm.cpl.mun
\Windows\SystemResources\sysmon.ocx.mun
\Windows\SystemResources\systemcpl.dll.mun
\Windows\SystemResources\tapiui.dll.mun
\Windows\SystemResources\Taskmgr.exe.mun
\Windows\SystemResources\themecpl.dll.mun
\Windows\SystemResources\themeui.dll.mun
\Windows\SystemResources\timedate.cpl.mun
\Windows\SystemResources\tquery.dll.mun
\Windows\SystemResources\TtlsExt.dll.mun
\Windows\SystemResources\twinui.appcore.dll.mun
\Windows\SystemResources\twinui.dll.mun
\Windows\SystemResources\usercpl.dll.mun
\Windows\SystemResources\VAN.dll.mun
\Windows\SystemResources\Vault.dll.mun
\Windows\SystemResources\wcnwiz.dll.mun
\Windows\SystemResources\wdc.dll.mun
\Windows\SystemResources\wiadefui.dll.mun
\Windows\SystemResources\wiashext.dll.mun
\Windows\SystemResources\Windows.Data.Pdf.dll.mun
\Windows\SystemResources\Windows.UI.Immersive.dll.mun
\Windows\SystemResources\Winlangdb.dll.mun
\Windows\SystemResources\wlangpui.dll.mun
\Windows\SystemResources\WlanMM.dll.mun
\Windows\SystemResources\wmploc.DLL.mun
\Windows\SystemResources\wpdshext.dll.mun
\Windows\SystemResources\wscui.cpl.mun
\Windows\SystemResources\wsecedit.dll.mun
\Windows\SystemResources\wuapi.dll.mun
\Windows\SystemResources\zipfldr.dll.mun

Boec.Nsyc
January 28th, 2020, 05:49 PM
Fireee!)):peace:

ミறѳѳղղįզվદ彡
January 28th, 2020, 08:26 PM
Fireee!)):peace:
:girl:

LegzRwheelz
February 6th, 2020, 11:17 PM
THis patches my icons just fine, however it makes some of my control panel windows unusable. I've attached a screenshot. Anyone else have this issue? I have tried googling to find some answers but no luck. This happened on a fresh windows 10 1909 install, after finding this version of 7tsp, I figured the problem was solved. It happens with iPack installers as well. So I know it is a windows issue, but if someone has an idea of what is causing the issue, please lmk. Thank you in advance

ミறѳѳղղįզվદ彡
February 7th, 2020, 02:06 PM
THis patches my icons just fine, however it makes some of my control panel windows unusable. I've attached a screenshot. Anyone else have this issue? I have tried googling to find some answers but no luck. This happened on a fresh windows 10 1909 install, after finding this version of 7tsp, I figured the problem was solved. It happens with iPack installers as well. So I know it is a windows issue, but if someone has an idea of what is causing the issue, please lmk. Thank you in advance
hello and yes this can broke your Control panel or File Explorer if you are using 7tsp Icon Pack not fixed for using on Windows 10 19h1+ with new .mun files
please can you upload here 7tsp Icon Pack what you are currently using and which broke your system

LegzRwheelz
February 8th, 2020, 07:29 PM
Hi moonique, I am using your dark red theme, both ipack and 7tsp break control panel. Here is the version I am using

ミறѳѳղղįզվદ彡
February 8th, 2020, 07:47 PM
Hi moonique, I am using your dark red theme, both ipack and 7tsp break control panel. Here is the version I am using
if you are on Windows 10 1903 19h1 or 1909 19h2 please do not use 7tsp Icon Pack w8 8.1 w10
Because this Icon Packs has been created and working only on Windows 8 8.1 and w10 TH2-RS5
if you are on Windows 10 1903 19h1 please use 19h1+ packs
this Icon pack can be used only with 7tsp v0.6 2019

LegzRwheelz
February 8th, 2020, 07:57 PM
EXCELLENT! Thank you so much. You, my friend are my hero <3

ミறѳѳղղįզվદ彡
February 9th, 2020, 10:36 AM
EXCELLENT! Thank you so much. You, my friend are my hero <3
youre welcome:Smile:

drmsalem
February 19th, 2020, 12:58 PM
looks nice

ZeroWolf
March 4th, 2020, 03:11 PM
what theme you using in this post

ミறѳѳղղįզվદ彡
March 4th, 2020, 05:57 PM
what theme you using in this post
hello and this is the Alienware Red theme with some MSI upgrades
but you can download original theme here
https://virtualcustoms.net/showthread.php/83694-Alienware-Red-Complete-pack-for-Windows-10-1903

snelle
May 11th, 2020, 05:57 PM
thx grts snelle Belgium

ミறѳѳղղįզվદ彡
May 11th, 2020, 11:41 PM
thx grts snelle Belgium
:girl:

ミறѳѳղղįզվદ彡
May 21st, 2020, 04:04 PM
Windows 10 May 2020 update 20h1 2004 OS build 19041
C:\Windows\SystemResources\themecpl.dll.mun
PNG and Bitmap files has been removed from the original file
C:\Windows\SystemResources\themecpl.dll.mun removed PNG (subfolder)
C:\Windows\SystemResources\themecpl.dll.mun removed Bitmap (subfolder)
86586

86587

86588

ミறѳѳղղįզվદ彡
May 21st, 2020, 04:45 PM
Windows 10 May 2020 update 20h1 2004 OS build 19041
C:\Windows\SystemResources\themecpl.dll.mun
PNG and Bitmap files has been removed from the original file
C:\Windows\SystemResources\themecpl.dll.mun removed PNG (subfolder)
C:\Windows\SystemResources\themecpl.dll.mun removed Bitmap (subfolder)
86586

86587

86588

Windows 10 May 2020 update 20h1 2004 OS build 19041
you need to create a new (subfolder) in the themecpl.dll.mun as (IMAGE)
C:\Windows\SystemResources\themecpl.dll.mun\IMAGE
all files here need to save as PNG
because Windows 10 20h1 now using
more of the new Glyph Icons and this Icons need be saved as PNG
not as .bmp .ico etc hope this help to you my friends
86589

86593

86591

86592

terminator9
November 18th, 2021, 01:20 PM
merci

DaRkCaSTLe
March 2nd, 2022, 07:00 AM
this will rule with my full on MSI machine