How to disable FoDMetadata_Client?

FoDMetadata_Client restores files deleted by NTLite after installation when connected to the Internet.
 

Attachments

  • 1.jpg
    1.jpg
    469.2 KB

garlin

Moderator
Staff member
The only way is to disable Windows Update. Add Features checks this updated metadata to know new Features are available.
 
The only way is to disable Windows Update. Add Features checks this updated metadata to know new Features are available.
How can I disable it? I even deleted the Windows update center itself for the sake of an experiment on a freshly installed system and it didn't help.
 

garlin

Moderator
Staff member
OOBE (Out of Box Experience) runs WU during install, even if you disabled it. Don't worry about those files, it's just metadata.
If you're really concerned, unplug the network or block your machine when installing.

But if WU runs again, it will look for FOD metadata. There is no setting for this, sorry.
 
OOBE (Out of Box Experience) runs WU during install, even if you disabled it. Don't worry about those files, it's just metadata.
If you're really concerned, unplug the network or block your machine when installing.

But if WU runs again, it will look for FOD metadata. There is no setting for this, sorry.
Have you tried any settings for sure? And for example editing the ActionList file may help or editing the CAB archive FoDMetadata_Client or DesktopTargetCompDB_Neutral.xml . Just then what's the point of deleting them with the NTLite program if they are restored anyway. And I noticed these files slightly affect the color of the desktop image clarity and brightness, etc.
 
Last edited:

garlin

Moderator
Staff member
OOBE WU updates any installed Features or UWP (Store) apps it finds with newer versions. OOBE uses the same tools as WU, but ignores any of those settings. The only way is to block network access during install.

One trick is to use a fake WSUS server (localhost). WU will timeout and do nothing.
If you want, integrate this reg file (don't add as Post-Setup item).
Code:
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate]
"DoNotConnectToWindowsUpdateInternetLocations"=dword:00000001
"WUServer"="127.0.0.1"
"WUStatusServer"="127.0.0.1"

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU]
"UseWUServer"=dword:00000001

If you want WU to work again after OOBE, add this regfile to Post-Setup:
Code:
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate]
"DoNotConnectToWindowsUpdateInternetLocations"=-
"WUServer"=-
"WUStatusServer"=-

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU]
"UseWUServer"=-

This will stop the unwanted feature changes on setup. After this, it's back to normal WU behavior.
 
OOBE WU updates any installed Features or UWP (Store) apps it finds with newer versions. OOBE uses the same tools as WU, but ignores any of those settings. The only way is to block network access during install.

One trick is to use a fake WSUS server (localhost). WU will timeout and do nothing.
If you want, integrate this reg file (don't add as Post-Setup item).
Code:
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate]
"DoNotConnectToWindowsUpdateInternetLocations"=dword:00000001
"WUServer"="127.0.0.1"
"WUStatusServer"="127.0.0.1"

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU]
"UseWUServer"=dword:00000001

If you want WU to work again after OOBE, add this regfile to Post-Setup:
Code:
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate]
"DoNotConnectToWindowsUpdateInternetLocations"=-
"WUServer"=-
"WUStatusServer"=-

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU]
"UseWUServer"=-

This will stop the unwanted feature changes on setup. After this, it's back to normal WU behavior.
Thanks! Since the days of Windows 7, I realized that you need to disconnect the network when installing the system. I never use updates, they fix one thing and break another. The update center is tied to the power supply, I do not delete it because it breaks the sound in the system, any reg keys to block updates also break the sound, in any case, the bass disappears on my equipment and the sound becomes not soft, but very sharp. I'll save the reg file just in case. I edited the ActionList file, connected to the Internet and everything is fine so far, the files are not being restored, I will also leave it overnight with the Internet turned on. If everything works out, the main thing is that the installation is successful with the edited file.
 
OOBE WU обновляет все установленные функции или приложения UWP (Store), которые он находит, новыми версиями. OOBE использует те же инструменты, что и WU, но игнорирует все эти настройки. Единственный способ — заблокировать доступ к сети во время установки.

Один из приемов — использовать поддельный сервер WSUS (localhost). WU истечет время ожидания и ничего не сделает.
Если хотите, интегрируйте этот reg-файл (не добавляйте его как элемент Post-Setup).
[КОД][HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate]
"DoNotConnectToWindowsUpdateInternetLocations"=dword:00000001
"WUServer"="127.0.0.1"
"WUSatusServer"="127.0.0.1"

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU]
"UseWUServer"=dword:00000001[/CODE]

Если вы хотите, чтобы WU снова работал после OOBE, добавьте этот reg-файл в Post-Setup:
[КОД][HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate]
"DoNotConnectToWindowsUpdateInternetLocations"=-
"WUServer"=-
"WUSatusServer"=-

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU]
"ИспользоватьWUServer"=-
[/КОД]

Это предотвратит нежелательные изменения функций при настройке. После этого он возвращается к нормальному поведению WU.
On 19 H2, the trick with editing the ActionList file worked, but on 21 H2 it did not, the ActionList file was restored when connected to the Internet. Checked on the installed system. Are you not aware that Microsoft has changed something in 21H2 or perhaps another reason?
 
Last edited:

garlin

Moderator
Staff member
I don't edit ActionList or any files in there. That doesn't always work, because you have to catch WU in the right moment.
 

Necrosaro

Member
There is a program on steam that stops windows update and even more. The app on the web is WDP(will have to make another post of the app on steam since I forget the name) privacy dashboard for Windows. Works well and easy enough to stop and start things you need.
 

Clanger

Well-Known Member
Sledgehammer by pf100 is better at controlling WU in my opinion. Registry edits/disabling your internet connection are the only options during setup.
 

Saaglem

Active Member
You can run this. It will block your firewall. You can include it into your "setupcomplete" command file.

powershell -Command Set-NetFirewallProfile -DefaultOutboundAction Block

Once you installed everything you can just reset your firewall to default, windows defender, advanced, action, reset to default. This will block your windows from going online during install.

Cheers
 

garlin

Moderator
Staff member
Don't forget SetupComplete runs after OOBE. Fixing the firewall rules won't block anything before this stage.
 
Top