Hi Kris,
I have had this problem happen to me several times in the past and have even had this happen to me today. Oddly enough, SEPM has some weird behavior.
Here is my scenario, and hopefully will point you in the right direction for yours, also here are some ways "I can force the loop".
* * * * * * * *
SEP installed on ALL clients in my Domain are installed in c:\Symantec (This allows me to have a standard install in 32 and 64 bit).
All my user accounts have been moved from "C:\documents and settings..." to "D:\Windows\Profiles\[user name]"
* * * * * * * * *
If I want to force a Loop of the installer, I start a command prompt and:
chkdsk /X d:
This prompts me to unmount the Volume before checking. If I say YES to this, the Symantec Installer goes crazy and begins to loop. The only reason I could see why it would do this, is it depends on some files in the %user% folder in order to run properly. Normally, this is supposed to be "priviledged space" and should not require any kind of interaction from a local user. But it doesn't.
So, what I would do, if I was you and wanted to test this theory... do you have a test machine?
I know it works in my environment. I can do it anytime I like. I should probably even FRAPS it and post the video of me doing so Symantec can address the issue.
From any machine, that is currently looping, either
login as administrator or open a command prompt and type:
"runas /noprofile /user:[domain]\administrator cmd"
It will prompt you for the domain admin password. Once entered will open a new prompt. This will be an administrative prompt. In this new prompt, type:
cacls [location of user profiles] /E /T /G everyone:F
** In my case the command would be:
cacls D:\Windows\Profiles /E /T /G everyone:F **
This will modify the current "security" policies on the folders contain therein, maintaining the existing, but adding FULL control to "everyone".