Could anyone from inhouse installers team give a try on this.

Hi. Chrome and its installer require that these environment variables:

%PROGRAMFILES%
%PROGRAMFILES(X86)%
%PROGRAMW6432%

and these KNOWNFOLDERID values:

FOLDERID_ProgramFiles
FOLDERID_ProgramFilesX64
FOLDERID_ProgramFilesX86

Point to sensible and consistent locations. Please check that your method of moving your program files directory results in all of these being correct.

While you're off into unsupported territory with these changes you're making (both in the case of Windows and Chrome), we could try to make it work. If the only problem is that the rename of new_chrome.exe is failing, then it should be enough to bring up the browser, start logging, and quit the browser. It should attempt the rename during shutdown. That log *might* help us identify what's going wrong.

Cheers.

So, using both powershell and command line, the registry edit does reflect in both the environment variables and known folder id's.
More testing on my side is going to have to happen but i would need to find an older version of chrome to do a test for this.
Otherwise, the error shown in the about chrome might also reflect on the google update service not liking these folder paths changing.
Heck, I've had a few different programs freak out because of the change.

Correction, the environment variable %PROGRAMW6432% is not reflected.
Still points to the C drive instead of the D drive.

FWIW for such cases you can keep an NTFS junction at the old location that redirects to the new one.
mklink /j "C:\Program Files" "D:\Program Files"

That would work if I have all program files off of the C drive.
As my setup is, I have it configured as followed:
-C drive is for programs that need to load fast, i.e. Syncthing, LinkShellExtention, HWiNFO, etc.
-D drive is for programs for general programs, such as 3D modelers, games, etc.
So, symlinking/junctioning the program folder is not viable.

@grt: Could you please take a look into this issue.Thank You!

You can symlink/junction a single folder (Chrome or Google or whatever) inside "c:\program files" that points to your other drive's counterpart.

As this issue is related to Internals>Installer and is out of scope of triaging at TE end, adding 'TE-NeedsTriageHelp' and requesting the appropriate team to look into the issue and help further.

Thanks..