Unified telemetry client asimov depends on windows error reporting

I started this new topic to keep together different tools and procedures available to reduce the used size of the OS.

I had the idea when making post: http://reboot.pro/to…-14#entry216443

• Detailed procedures.
• Clear info.
• Advantages and disadvantages (if any).
• Possible issues (if any) and how to fix them.
• Pictures.
• Links of tools used.

EDIT: During the tests ran for this topic we have achieved a 1.57 GB used size on a 2.3 GB VHD, by means of cutting several non critical parts on the 10 OS.

Our fellow wimb making use of his skills on AutoIt3, was able to put together all the info we have gotten on this topic, about cuttings and related to some programs, and also about some free portables, and made a program capable to do all this automatically in less than a minute.

• Win_Reduce_Trusted v4.0 (valid for 10, 8.1 and 7) links are on post No. 429,
• Install and run Office 2003, info on Post No. 179
• Additional info for Win_Reduce_Trusted is on post No. 339.
• Additional files required to keep to run LibreOfficePortable (multilang) are on Post No. 340.
• Interesting info when using NTFS Compression + Compact LZX compression on Post No. 341.
• Additional info about LibreOfficePortable on this Post
• New info from wimb about LibreOfficePortable on Post No. 429
• Additional useful links for your Mini-10×64-2004.vhd on this Post and this Post.
• What to do in case you find some issues with your favorite programs, see Post No. 376
• Remote image capture and deploy by means of Mini10x64.vhd and TeamViewerPortable, see post No. 430

alacran

• wimb and Tokener like this

Reduce the install.wim file Index(es)

I usually use MSMG ToolKit a free tool to remove safely from the install.wim index(es) all things I don’t like/use on my installed OS, also some redistributables as DirecX, .Net Framework, VCC++, etc., can be added with this tool, just read carefully the included README.txt, to start running it just run as Admin the Start.cmd, this tool is basically a long script (1.50 MB +) that let you select the ISO, and extracts folder sources content to its ToolKit_vxx.x\ISO\sources folder, then you can select the Index(es) where you want to make the changes, boot.wim and recovery.wim can also be selected, then the WIM(s) are mounted using Dism to its ToolKit_vxx.x\Temp folder, and all removed or added is made by Dism, see attached picture of Main Menu.

As the subject of this topic is related to reduce the size of the OS, I will talk only about the options related to this matter, following is a compilation I made (from the Toolkit.cmd) of the windows presented to the user, when selecting the available options related to remove, deactivate certain options or characteristics, I included only those related to 10 v2004 to make this shorter but the script can be used from 7 to 10 and it is coded with the options that apply for each version.

alacran

Multi-OEM/Retail Project {MRP} — Mk3

You need to be or become a member to open the link.

This tool DO NOT contain any cracks, malware or telemetry into it, and is very usefull to create a $OEM$ folder that will be used during installation to make a tailored installation according with our preferences, adding certain usefull items and/or removing/unactivating certain unwanted characteristics, and it is also usefull to highly reduce the OS telemetry, for more info take a look to the attached pictures of my usual settings.

This program works from 7 to 10, x86 and x64, under Bios or UEFI environments.

alacran

• wimb likes this

Reduce the OS after installed.

In the quote of first Post there is a comment about WinSxS_Reduce_Trusted this is a tool made by wimb based on cdob commands, what it does is reduce the content of Windows\WinSxS folder, during some test ran on 10×64 Compact LZX installed and using cdob commands got a reduction of about 0.85 GB of used size by the OS, (only valid for 10).

From: http://reboot.pro/to…ls/#entry215543

Comparing LZX and LZX Reduced there is a saving of 0.85 GB, lets say almost 1 GB

I also mentioned the OS can also be reduced if we edit the WimBootCompress.ini [ExclusionList], but this requires to capture and reinstall it, this apply from 7 to 10.

In fact our current modified WimBootCompress.ini [ExclusionList] section already contains this two lines to reduce the used size comsumed.

[ExclusionList]
\MSOCache\* >>>  This is from MS Office installation, usually from 250 MB to about 1 Gb depending of the program version.
\Recovery\*  >>>  This is 165 MB on 7 and about 420 MB on 10.

So far all reductions/deletions are safe and do not remove any critical characteristic of the OSs.

Of course there may be other files/folders that could be added to WimBootCompress.ini [ExclusionList] but as also said on the quote on first Post:

Then any files/folders added by the user to [ExclusionList] section will not be included on the new WIM file (no matter the consequences), edit it wisely to avoid future troubles after apply the new WIM on a new installation.

In fact it is as a chopping by brute force.

I invite all readers of this topic to share their experiences when chopping the OS.

alacran

• wimb likes this

After using WinSxS_Reduce_Trusted,

I did some brute force chopping in Win10XPE on mounted Win10x64 VHD and removed folders SysWOW64 and Microsoft.NET and 

the NVIDIA DriverStore folder \Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_90685a092bcf58c7

After Chopping then Win10x64 is still booting fine, but we don’t have support for 32-bits and .NET apps anymore.

 Chopped_2020-10-04_065558.jpg   347.8KB
  0 downloads == 
 Chopped_sshot-1.png   547.45KB
  0 downloads

• alacran likes this

Good test.

EDIT: But from your pictures the gain in saved espace is only 0.46 GB, so it isn’t a big gain, I should expect bigger gain.

Was the VHD Compact LZX?

And I assume now you will have a lot of Error events on the Event viewer >>> Windows logs (maybe other words, mine is in spanish Registros de Windows) on Application, Safety, Installation and System sections.  Please would you check this?

By the way I have some time trying to stop so many reports and logs mainly saying something is working fine, and I would like to have and keep info only when something is not working fine.

From a link on a Wonko’s post: http://reboot.pro/to…13#entry216280 on this link: https://superuser.co…s-10-system-log

I tried the suggested command: auditpol /set /subcategory:»Filtering Platform Connection» /success:disable /failure:enable, but it is not acepted the message said only one command by execution is allow.

alacran

Good test.

EDIT: But from your pictures the gain in saved espace is only 0.46 GB, so it isn’t a big gain, I should expect bigger gain.

Was the VHD Compact LZX?

The comparison is a good illustration but not really valid to make conclusion about saved space.

The comparison is between different VHD’s where the same WIM file was applied but with different history ….

The left panel is the Chopped Win10x64 and includes New Edge, whereas the right panel is reduced with WinSxS_Reduce_Trusted only and where New Edge was Not Installed.

Strange thing is that 64-bits New Edge is Installed in C:\Program Files (x86)\Microsoft and can be used when SysWOW64 folder has been removed !!!! 

==

The change in System32 and SysWOW64 and Microsoft.NET folders is evident ….

It is indeed Compact LZX Applied by VHD_WIMBOOT

I need to view the Error events logs, but until now everything for 64-bits apps is working fine

And I assume now you will have a lot of Error events on the Event viewer >>> Windows logs (maybe other words, mine is in spanish Registros de Windows) on Application, Safety, Installation and System sections.  Please would you check this?

There are no Event viewer > Windows logs available in my Chopped / Reduced Win10x64 VHD 

As you can see 64-bits Edge is Installed in C:\Program Files (x86)\Microsoft\Edge\Application

 Edge_sshot-1.png   143.49KB
  0 downloads

brute force is the most effective!!! jokes apart, can u have .net and 32bit apps working without syswow64 now?

syswow64, as the name implies (in the perverted minds of the good MS guys) is actually the 32 bit sub-system on 64 bit OSes:

https://www.samlogic…86-syswow64.htm

so allow me to doubt that 32 bit apps will work without syswow64.

Wonko

EDIT: But from your pictures the gain in saved espace is only 0.46 GB, so it isn’t a big gain, I should expect bigger gain.

Was the VHD Compact LZX?

I repeated the experiment VHD with Compact LZX fresh Win10x64 2004 + Office2003 Integrated until 2014 + 7-zip + VLC Player + registrybackup — UsedSize = 5.27 GB

After WinSxS_Reduce_Trusted then UsedSize = 4.58 GB and the Reduction Effect = 0.69 GB

After Chopping SysWOW64 and Microsoft.NET and NVIDIA DriverStore folders then UsedSize = 3.70 GB and the Reduction Effect = 0.88 GB

Compact LZX  == WinSxS_Reduce == Chopped SysWOW64 and .NET and NVIDIA == Mount VHD in other W10x64 == and Mounted in 10XPE == Chopped assembly

 Chop_0_2020-10-04_140318.jpg   345.55KB
  0 downloads == 
 Chop_1_2020-10-04_140547.jpg   346.51KB
  0 downloads == 
 Chop_2_2020-10-04_141051.jpg   344.57KB
  0 downloads == 
 Chop_3_2020-10-04_152316.jpg   147.14KB
  0 downloads == 
 Chop_4_2020-10-04_154302.jpg   346.99KB
  0 downloads == 
 Chop_5_2020-10-04_164538.jpg   344.29KB
  0 downloads

New Edge is Not Installed !!

— After WinSxS_Reduce_Trusted and Chopping SysWOW64 and Microsoft.NET and NVIDIA DriverStore folders then still booting FINE 

EDIT: After Booting VHD followed by Mounting VHD in Other Win10x64 there is remarkable change in System32 and in Program Files and in ProgramData folders 

What is Next to be Chopped Or are we Finished …? No, we can chop assembly folder (part of .NET) gives UsedSize = 3.54 GB and Reduction Effect = 0.16 GB

What would stop working with this latest chopping of yours? 

What would stop working with this latest chopping of yours?

.NET Apps ….

If you chop SysWOW64, Office version installed has to be x64 or it will not work, also PS.exe, Pstart.exe, aida64.exe and a big etc. will not work.

I suggest to not chop it and better reduce SysWOW64 as on Win10XPE_x64 (size 174 MB), attached the list file used: WoW64_AddFiles.

EDIT: The minimum files we need to keep are those allready on the wimre.wim + all added by the attached list.

About chop Microsoft.NET, a lot of .Net files still remain on other locations see attached picture, but they should be easily deteted searching for .NET on SwiftSearch, selecting all of them and right click delete.

alacran

• wimb likes this

If you chop SysWOW64, Office version installed has to be x64 or it will not work, also PS.exe, Pstart.exe, aida64.exe and a big etc. will not work.

I suggest to not chop it and better reduce SysWOW64 as on Win10XPE_x64 (size 174 MB), attached the list file used: WoW64_AddFiles.

This are the minimum files we need to keep.

About chop Microsoft.NET, a lot of .Net files still remain on other locations see attached picture, but they should be easily deteted searching for .NET on SwiftSearch, selecting all of them and right click delete.

alacran

Good idea and Thanks for the minimal SysWOW64 filelist 

More and more it sounds like the approach of Mini 7 and Mini 8,

where the filelist of PE was used as minimal needed files combined with the full registry of installed 7 / 8

Hello World — Mini 10 is coming …. 

but still not really needed since we have WimBoot for booting from RAMDISK with UsedSize 200-600 MB

and for FILEDISK a few extra GB is No problem nowadays …. Nevertheless we try what can be realised with chopping 

Actually I am surprised that Win10x64 allows so easily all this chopping ….

Interesting could be that we end with small VHD booting from RAMDISK without being connected to the large WIM file

and that we can modify that VHD by booting as FILEDISK e.g. for Install of small program, which is not possible in PE.

I think it can work ….

JFYI

After apply WinSxS_Reduce_Trusted, and remove SysWOW64 and Microsoft.NET by brute force, made last night.

The Windows Event viewer do not work, but if going to %WinDir%\System32\\winevt\Logs we can see all *.evtx files are there.

I copied from my mounted Win10XPE_x64_LZX.vhd the SysWOW64 folder and now 32 bits programs are running fine.

And also deleted:

About chop Microsoft.NET, a lot of .Net files still remain on other locations see attached picture, but they should be easily deteted searching for .NET on SwiftSearch, selecting all of them and right click delete.

I got two messeges when booting, sorry i wasn’t able to capture the screen, but as now 32 bits programs are running fine I was able to run aida64.exe portable to take a look to the Events.

EDIT: Before deleting the remaining .NET files it was booting fine, no messages so I think it is better not do this. The info for the Errors was not helpful, just vague info or nothing, but I think it is related to the 2 messages when booting and also the Event viewer not working when running it.

alacran

• wimb likes this

After chop System32\WinBio folders and C:\Windows\System32\DriverStore\FileRepository\helloface.inf_amd64_5fda9eda33bf7e67 and all Asian Fonts

 Chop_6_2020-10-04_213111.jpg   148.73KB
  0 downloads

What’s next. Until now no problem with chopping ….

Nice to hear that 32-bit apps are working with Reduced SysWOW64 

Maybe all *.mui files not in your language.

alacran

After checking Windows\System32 I found all non es_MX or es_ES (in my case), are only about 48 MB, so it will not be a big gain, but anyway I never use them.

alacran

In general we can try to reduce System32 to a level more corresponding to 10XPE ….

Removal of System32\Speech can be tried as well, and System32\migwiz

Also we can compare with Portable / Mini 8 FileLists in folder VHD_W8C_88\VHD_W8 ( copy_8vhd.txt and mini_8vhd.txt etc)

How about syswow64 subfolders? do they go away or are they kept?

have u really tested what u are advocating? I have, and either it does not work or I am a total fool.

… either it does not work or I am a total fool.

tertium non datur …

https://en.wikipedia…excluded_middle

according to Quelo :

https://it.wikipedia…a_che_hai_detto!

Wonko

• antonino61 likes this

hhahha, wonko, albeit in ur own way, u r wonderful. I really did try hard in testing it, left, right and center, I really do not know whether I shoulda run it all as ti but i did as admin, honestly. is this the tertium datur, or did they go by analogy with mini8 or winpe? I am desperate for something that could support my chopping, which is of the «do everything but fix the mislinks» type, at least, to the best of my knowledge (which is slight) and belief (which is huge).

@everyone of good intellect&understanding

i guess healthy competition for the smallest os, which, believe me, is useful, and not only a curiosity, must be gauged on the wim, not on the vhd. I have the smallest 19041/2 264 build combo (vhd+wim) below 3gb put together (of course vhd.gz 15megs). all this was done with my chopping sequence, which could be coupled with any further and wider chopping. of course. I am now trying an older version. I can easily keep my chopping under control, even though it was decided against, but no prob, i will let u know. the only problem is time.

BernieK

A couple of guys (and I) made this test in France: Thoses having the most optimized versions of WS16 or WS19 (AO3, Fidelizer, Process Lasso…) does prefer the WS setup.

By the way, LTSC is a must have, more affordable, better drivers friendly, to begin a very good musical  PC.

Last week i implemented LTSC on a server/streamer i made for a friend who has an excellent system; the music is astounding and my friend is delighted.

• Marcin_gps, BernieK, motberg and 1 other like this

Hifi must serve the Music.

Not the opposite

It would be interesting to know whether AO 3.0 improves the sound quality of Windows 10 LTSC and whether that combination provides better sound quality than Windows Server 2019 plus AO 3.0.

Are you using AO ?

Yes, moved from 2019 GUI AO3 to LTSC AO3 on both machines.  No other S/W other than JPLAY (FEMTO as renderer).

‘Better’ is subjective and I cannot categorically say it is in all regards. The main improvement for me is the extra air and sparkle that benefits the leading edge of music and timing. I listen to a lot of dance music (revisiting a lot of DJ mixes from the late, great Andy Weatherall at the moment) and LTSC is sounding more exciting than 2019 did. I did note a possible increase in graininess initially but not anymore, so maybe it still exists but I got used to it. That could be one downside but certainly doesn’t outweigh the benefits for me. 

It would be interesting to know whether AO 3.0 improves the sound quality of Windows 10 LTSC 

TBH, I didn’t notice any obvious difference between running LTSC with AO and without it, but I have a lot of noise around here at the moment (lol), so am not the best person to comment. Maybe someone else could compare and report back.

There was some unusual behaviour with installing the AO3 set up file; It gave a message about ‘enabling drivers and services’ (as if already installed) and then restarted unexpectedly. It also didn’t leave any shortcuts on my desktop. Once installed and AO enabled, my adapter in network connections is still visible!  But it seems to be working as normal (as seen in device manager) and I would like to try the W10 strip down feature if it doesn’t lead to any conflicts or instability. Anyone tried that?

• BernieK, motberg, Chanh and 2 others like this

I’d use Windows 2019 IoT LTSC now which is the smallest footprint Windows version available now.  

It is used in Taiko Audio SGM Extreme server. 

The OS can be tweaked further. 

Hi Marcin, what’s your view on this version called Win10XPE since that’s MUCH smaller than LTSC?

It seemed to have the necessary components for audio and networking already

https://github.com/ChrisRfr/Win10XPE

http://win10se.cwcod…essed/index.php

Win10XPE HomePage (Moderator: ChrisR)

Win10XPE — How To Quick Start Guide

http://theoven.org/i…hp?topic=2569.0

Audio

Network additions and Network drivers

Microsoft-Windows-WinPE-AudioCore(AudioDrivers)-Package

Win10XPE Optional Member XPE APP’s

http://theoven.org/i…hp?topic=2607.0

MS Windows Media Player

Media Player Classic-Black Edition *

VLC Media Player *

Many thanks for this info seeteeyou but, for example, it seems to be impossible to install JPLAY  as there is no portable version. 

PE should be even better — if all components we need are there. 

I can’t access these links without loggin in, so can’t say.. 

Regards, 

Marcin

Follow my hi-fi journey on YouTube

As WinPE is no persistent it’s difficult to use.

• motberg likes this

Regarding that 72-hour limit, it’s already explained here

http://www.boot-disk…uest_reboot.htm

https://techtalkpro….ns-preperation/

Link to the official PsSuspend64.exe created by Microsoft

https://live.sysinte…pssuspend64.exe

https://docs.microso…loads/pssuspend

pssuspend64.exe winlogon.exe
pssuspend64.exe wininit.exe

So basically my colleague and I were already using this version of PE created by Mike Wang (i.e. NoName Team @ Taiwan) in a corporate environment for many years already, here’s a link to the latest version 19041.330 and it’s under 500 MB

https://drive.google…FG1_gtWnRU/view

https://inonameteam….d-3412-1-1.html

Just in case the link to Google Drive might be changed later, please kindly look under the folder 0_10PE and then click the link right below 10PE19041x64_T.iso afterwards

https://sites.google…te/toolsdnpe/pe

Since the user interface is only available in Chinese while that sources\boot.WIM image inside the ISO couldn’t be mounted with neither DISM command nor PowerShell cmdlet, there’s no way to convert that into the VHD format as shown in the very first link of this reply.

I extracted sources\boot.wim images from two regular Windows 10 setup ISO files downloaded from Microsoft, both of them were converted into VHD just fine.

From the perspective of troubleshooting, it wouldn’t be so much fun to deal with Rufus in order to create UEFI bootable USB flash drives. I could handle that on my own but sometimes it’s a different story if we’re trying to troubleshoot something over the Internet without looking at it in person.

If you want something done right, do it yourself. Most likely it’s a good idea to build an image ourselves with either WimBuilder2 or Win10PE SE as follows, both of them already came with the options to add networking and audio components by default

https://github.com/s…nts/02-Network/

https://github.com/s…nents/03-Audio/

http://hello.wimbuilder.world

https://www.tenforum…escue-disk.html

http://win10se.cwcod… drivers.script

http://win10se.cwcod…s/Audio8.Script

• Marcin_gps, Mellowman, DC and 2 others like this

Interesting stuff that might be worth a try?

Windows 10 Starter

Windows Editions Reconstruction Project

https://forums.mydig…18#post-1605010

starter_standalone_15063.0_x64_en-us

1. Place install.wim of 15063.0 Windows 10 Home (en-US amd64) into starter_standalone_15063.0_x64_en-us folder

2. Run command prompt as Administrator

3. Change path to X:\starter_standalone_15063.0_x64_en-us

4. Input or paste full_build.cmd and press Enter to start

Difference between 15063.0 Core and Starter:

The Windows Starter edition only includes few Features.

15063.0 Starter for example.( Long list. Actually several Features only.)

15063.0 Windows 10 Home (en-US amd64) could be downloaded from official Microsoft servers as linked below

Windows 10 1703 (Redstone 2)

https://tb.32767.ga/get.php?id=361

Microsoft Windows and Office ISO Download Tool

https://www.heidoc.n…o-download-tool

Security updates

2020-06 Servicing Stack Update for Windows 10 Version 1703 for x64-based Systems (KB4562250)

2020-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4567516)

2020-06 Security Update for Adobe Flash Player for Windows 10 Version 1703 for x64-based Systems (KB4561600)

BTW, whole bunch of components could be removed from LTSC easily but not sure if that were compatible with 15063.0 (i.e. Windows 10 Version 1703) or otherwise

https://msmgtoolkit.in/download.html

Hello, I’m looking for Microsoft specialists feedbacks. According to few feedbacks including the ones from Mr Fidelizer, the version of Win10 update 2004 is a good reference for computer audio.

Would somebody know if the 2004 version for Windows 2019 Server (if i understand well 2019 Server is LTSC) has been released as i cannot find it.

Best regards

1) Install whatever version you can get (e.g. 1909)

2) Run Windows Update to get 2004

Windows Server is not LTSC and LTSC can’t be updated to 2004.

Have you manually clicked «Check for updates» in the Windows Update window?

Well that’s strange. Microsoft is rolling out the update just for small number of users at the moment, but you should be able to get the update by manually clicking on the «Check for updates» button. More info here

Are you sure you are running Windows Server and not the LTSC? LTSC can’t be updated as I have said.

I’m running Windows Server build 2004 on multiple machines.

Just to be clear folks, on the eval page it’s ISO-LTSC -> 17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x64FRE_en-gb.iso

Hello HungryBear, i’m running Windows 2019 Server Standard 1809 version 17763.1369.

It seems there is a difference between «windows server» that could be updated to the 2004 build and the Windows 2019 Server that seems to be LTSC and not possible to update.

Ah, upon further research, there really are LTSC versions of Windows Server. The update would not be possible then.

Sorry, my mistake.

I’m afraid such versions aren’t available for common people… 

We must have a VLSC account.

Such an interesting version here

https://forums.mydig…30#post-1621129

Don’t forget about checking en_windows_server_2019_x64_dvd_3c2cf1202.iso with Windows and Office Genuine ISO Verifier first

https://genuine-iso-…fier.weebly.com

Finding a copy of en_windows_server_2019_x64_dvd_3c2cf1202.iso on Google with ease

https://www.google.c…d_3c2cf1202.iso

Then extract that genuine file 4\sources\install.wim with 7-Zip afterwards.

• Chanh likes this