"Please disable all mods in NMM"

[dbulm2]

I had this same problem. It seems like deleting "C:\Games\Nexus Mod Manager\Skyrim\Mods\VirtualInstall\ fixed it.

[cfreak0]

Deleting the whole VirtualInstall folder isn't neccessary.

 

I found that Vortex continued to think I had mods enabled until I went to my VirtualInstall folder and edited the VirtualModConfig.xml file.

 

In the VirtualModConfig.xml file there was an old mod that must be from a previous installation. I deleted this node from the <modList> so that the file showed like this:

<?xml version="1.0" encoding="utf-8"?>
<virtualModActivator fileVersion="0.3.0.0">
  <modList></modList>
</virtualModActivator>

Vortex then was able to continue successfully with the mod import process.

Edited March 19, 2020 by cfreak0

[voltereta]

Th

 

  On 3/19/2020 at 1:38 PM, cfreak0 said:

Deleting the whole VirtualInstall folder isn't neccessary.

 

I found that Vortex continued to think I had mods enabled until I went to my VirtualInstall folder and edited the VirtualModConfig.xml file.

 

In the VirtualModConfig.xml file there was an old mod that must be from a previous installation. I deleted this node from the <modList> so that the file showed like this:

<?xml version="1.0" encoding="utf-8"?>
<virtualModActivator fileVersion="0.3.0.0">
  <modList></modList>
</virtualModActivator>

Vortex then was able to continue successfully with the mod import process.

Thank you so much, I did what you said and my mods started importing in no time!

[PopeSquid]

  On 3/19/2020 at 1:38 PM, cfreak0 said:

Deleting the whole VirtualInstall folder isn't neccessary.

 

I found that Vortex continued to think I had mods enabled until I went to my VirtualInstall folder and edited the VirtualModConfig.xml file.

 

In the VirtualModConfig.xml file there was an old mod that must be from a previous installation. I deleted this node from the <modList> so that the file showed like this:

<?xml version="1.0" encoding="utf-8"?>
<virtualModActivator fileVersion="0.3.0.0">
  <modList></modList>
</virtualModActivator>

Vortex then was able to continue successfully with the mod import process.

 

Hey there, Thank you for posting this tidbit, I was able to edit the file as shown but I'm still receiving the same message when I try to import. I'm leaning to cutting my losses and redownloading mods if this is the final option to fix said issue.

[PopeSquid]

  On 5/12/2020 at 8:03 PM, PopeSquid said:

 

  On 3/19/2020 at 1:38 PM, cfreak0 said:

Deleting the whole VirtualInstall folder isn't neccessary.

 

I found that Vortex continued to think I had mods enabled until I went to my VirtualInstall folder and edited the VirtualModConfig.xml file.

 

In the VirtualModConfig.xml file there was an old mod that must be from a previous installation. I deleted this node from the <modList> so that the file showed like this:

<?xml version="1.0" encoding="utf-8"?>
<virtualModActivator fileVersion="0.3.0.0">
  <modList></modList>
</virtualModActivator>

Vortex then was able to continue successfully with the mod import process.

 

Hey there, Thank you for posting this tidbit, I was able to edit the file as shown but I'm still receiving the same message when I try to import. I'm leaning to cutting my losses and redownloading mods if this is the final option to fix said issue.

 

 

Nevermind! ^^; I was able to figure this out myself, I did a once through and found a Mod folder in the load out that I didn't disable completely. Again, thank you for posting.

[AgentSabre]

This worked flawlessly, thank you.
(Just remember to Open With > Notepad.)

 

  On 3/19/2020 at 1:38 PM, cfreak0 said:

Deleting the whole VirtualInstall folder isn't neccessary.

 

I found that Vortex continued to think I had mods enabled until I went to my VirtualInstall folder and edited the VirtualModConfig.xml file.

 

In the VirtualModConfig.xml file there was an old mod that must be from a previous installation. I deleted this node from the <modList> so that the file showed like this:

<?xml version="1.0" encoding="utf-8"?>
<virtualModActivator fileVersion="0.3.0.0">
  <modList></modList>
</virtualModActivator>

Vortex then was able to continue successfully with the mod import process.

[Hycas]

Deleting the VirtualInstall folder fixed it for me, July 2020! Shame it can still happen but likely NMM not Vortex's fault, who knows. Just posting that it worked after deleting that folder.

[Deleted49955991User]

  On 2/28/2020 at 7:18 PM, dbulm2 said:

I had this same problem. It seems like deleting "C:\Games\Nexus Mod Manager\Skyrim\Mods\VirtualInstall\ fixed it.

THANK YOU!

[QUADPHONICS]

This is why I find Vortex to be a POS modding system. I don't know why this is not working, and honestly, the Nexus mod manager works so much better than Vortex. Granted, you have to use loot manager with Nexus mods, but it is still a better system than Vortex. Vortex is muddled and still very unstable, in my opinion, and it does not explain things properly.