Redmod stopping the compilation on temporary directory

[Guikingone]

Hi everyone, 

Small issue after a recent hardware change, I built a new PC and migrated my old C partition to a new one, things is, it seems that Redmod is using an old directory that no longer exist (because the SSD is removed from my machine), here's the error I'm facing (while launching it locally or via Vortex):
 

Commandlet deploy has failed.
Copyright (c) 2022-23 CD Projekt Red. All Rights Reserved.
Created in collaboration with CD Projekt Vancouver and Yigsoft LLC

Core: App instance InitializeCore in 0.00 ms
Continuing without global backend resource depot.
Core: App instance InitializeResources in 0.00 ms


[DEPLOY] Stage 1/5 - Initialization
Found mod "NIGHT CITY ALIVE" (v1.9 HIGH) in folder "NIGHT CITY ALIVE" (enabled; not deployed; TWEAKS; SCRIPTS; )
Needs deployment: true (FORCE)
[DEPLOY] Stage 2/5 - Script Compilation
default control path does not return a value:			 cyberpunk\UI\mappins\minimapMappins.script:618
Unknown opcode: SyntaxFloatConst
Unknown opcode: SyntaxArrayPopBack
Unknown opcode: SyntaxArrayPopBack
Unknown opcode: SyntaxConstructor
default control path does not return a value:			 cyberpunk\UI\mappins\minimapMappins.script:618
Unknown opcode: SyntaxBoolConst
Unknown opcode: SyntaxBoolConst
Core: [IO]: Low level create directory failed: path='E:\TEMP\', error code=0x3
Core: [IO]: CreatePath failed to create E:\TEMP error 3
Core: FileIO error at 'E:\TEMP\84305B5F-4F22A703-3A4F05A7-E6583D4E.tmp': Failed to create temporary file for saving 'E:\TEMP\84305B5F-4F22A703-3A4F05A7-E6583D4E.tmp' (temp file: 'C:\Cyberpunk 2077\r6\cache\modded\final.redscripts')
Core: Not saving content to 'C:\Cyberpunk 2077\r6\cache\modded\final.redscripts' because of IO errors during saving temp file 'E:\TEMP\84305B5F-4F22A703-3A4F05A7-E6583D4E.tmp'
Failed to open output file
ERROR: Script compilation has failed!

Commandlet deploy has failed.

The E drive is the one that has been removed and I don't know how to inform Redmod that it should use another one (I searched through the configuration files but nothing), to be transparent, I reinstalled the game in the new drive (NVME one) and verify/repair multiple times, same issue.

Any idea? Maybe someone already faced the situation? 

Thanks again for the help and have a great day.

Edited October 1 by Guikingone
typo