@x23piracy that did the trick for me, now i just need to read up on where to put that handy CMD file you wrote. thanks so much.

For those that are doing that post deployment where a user already logged in, had to reboot in safe mode, delete the files, remove the profile from profilelist in registry, change the folder name in c:\users\USERNAME to c:\users\USERNAME.BAK, reboot, and then the user logged in again and it was good.

thanks. I emptied the drivers folder and it went through - perhaps the extra script information will assist me to find out why it failed when i had drivers in it. let’s mark this resolved.

Which, after running the install script again, worked fine. Thanks, @Tom-Elliott

All set - it was the files being sent to a single filename * - that was just a syntax error on my part for using the Windows cli too often.

@Wayne-Workman - i had to change my /opt/fog/.fogsettings file back to pointing the storage at ‘/images’ because the entire imaging process breaks. Also re-added my /etc/fstab line to point /images to the home directory where the 177G volume is. I understand you think my system will fail if I fill up more than the 50G available on the root drive, I’m confident it won’t. Thank you greatly for your assistance, it was the file copy problem.

Fixing the chain bootloading issue on the other thread i posted here also fixed this kernel panic issue. thank you Tom.

@Tom-Elliott That did the trick, thank you.