[Solved]The specified module 'C:\Program Files\Microsoft Security Client\MpProvider' was not loaded because no valid module file was found in any module directory.

Hello,

This is happening again, when applying an update on development box, its failed with similar error on LCS

But when checking logs its says some strange error message, 

The specified module 'C:\Program Files\Microsoft Security Client\MpProvider' was not loaded because no valid module file was found in any module directory.

I could not find a permanent solution for this but below worked for me. Firstly you can try to resume it once if its still throwing errors try below steps, 

1. Do a get latest on your dev box
2. Clear any of your pending changes, if feasible. Or at least make them error free. 
3. Do a full build and synch, make sure there are no errors. 
4. Close the VS and any other application running on your machine. 
5. Close the RDP.
6. Try to update your VM now. 

Also check for similar issues while updating your development boxes, 

Update script for service model: DevToolsService on machine

-Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta

WorthKnowing: Where to add new fields on Item master

When customizing the item master in Dynamics 365 Finance and Operations (D365FO), one common question is:
Should I extend InventTable or EcoResProduct?

Here’s a WorthKnowing guide to help you decide:

1. InventTable

• Purpose: Holds inventory-specific data for released products.
• Scope: Company-specific (per legal entity).
• Use When:
  You need to add fields related to:
• Inventory management
• Warehousing
• Sales or purchasing
• Any data that varies by company
• Examples:
  Item group, inventory dimensions, default warehouse, sales price.

2. EcoResProduct

• Purpose: Stores the core product definition (product master).
• Scope: Shared across all companies (global).
• Use When:
  You need to add fields related to:
• Product identity
• Technical specifications
• Data that should be consistent across all legal entities
• Examples:
  Product name, product type, product number, technical specs.

Knowing the difference between these two tables can save you time and ensure your customizations align with D365FO’s architecture. Choose wisely based on the scope and nature of your data.

New post series 'WorthKnowing'

Hello Everyone,

I'm excited to kick off a brand-new blog series where I’ll be sharing bite-sized insights and interesting facts about Dynamics 365 Finance and Operations (D365FO).

This series will highlight:

• Hidden gems that have been around for a while but often go unnoticed
• New features and their best use cases
• Common functionalities you might be using differently than intended
• Similar looking things with their core differences

Each post will be short, sharp, and packed with useful takeaways to help you get the most out of D365FO.

Stay tuned — and let’s explore these insights together!

-Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta

How to Remove a Model or ISV Solution from Dynamics 365 Finance and Operations (D365FO)

Hi Folks, 

Removing a model or ISV solution from a Dynamics 365 Finance and Operations (D365FO) environment can be a necessary step during system cleanup, decommissioning unused features, or resolving conflicts. However, it must be done carefully to avoid breaking dependencies or corrupting the application metadata.

In this post I’ll Walk through the safe and structured process of removing a model or ISV solution from D365FO.

Before you begin, ensure:

• You have access to a development environment (Tier 1).
• You have admin rights in Visual Studio and Lifecycle Services (LCS).
• You’ve taken a full backup of model you want to delete/remove.
• You’ve identified dependencies and verified that no other models rely on the one you’re removing.

1. Identify the Model

Open Visual Studio in your D365FO development environment:

·       Go to Dynamics 365 > Model Management > Model Management.

·       Use the Model Util tool or PowerShell to list installed models:

Get-AXModel -Details

Identify the model name, publisher, and layer (e.g., ISV, VAR, CUS).

2. Check for Dependencies

Use the Model Dependencies Report in Visual Studio:

·       Go to Dynamics 365 > Model Management > Model Dependencies.

·       Select the model and generate the report.

·       Ensure no other models depend on the one you want to remove.

3. Uninstall the Model

If the model was installed via a deployable package (e.g., from an ISV), you’ll need to:

·       Remove the package from the AOSService\PackagesLocalDirectory.

·       Delete the model folder manually.

·       Optionally, use PowerShell: (This command only works for models installed via XPO or model store, not for package-based deployments.)

Uninstall-AXModel -Model <ModelName

4. Rebuild and Synchronize

After removal:

• Open Visual Studio.
• Rebuild the solution to ensure no broken references.
• Run Database Synchronization to update the schema.

5. Check in the changes

Do the code check in for deleted objects, make sure you select all deleted objects from your ‘pending changes’ tab.

6. Prepare package for Sandbox

·       Create DefaultModelDelete.txt This file tells the system which models to remove. It must contain the exact model name as registered in the model manifest. Just add exact model name in this file, if there are multiple models pl add into next line for example,

§  Model1

§  MyISVModel

• Create a new deployable package using your build pipeline or manually.
• Place the DefaultModelDelete.txt file in the root of the deployable package folder (same level as AXDeployablePackage).
• Ensure the model binaries and metadata are not included in the package.

7. Package deployment

·       Upload the package to LCS Asset Library.

·       Apply it to your sandbox or production environment.

·       Monitor the deployment logs for confirmation that the model was removed.

Removing a model—especially in production—requires precision and planning. Using the DefaultModelDelete.txt method ensures a clean and supported way to decommission ISV or custom solutions without manual intervention in higher-tier environments.