I have been trying to further integrate the KDEWIN into my window 7 OS by creating a service used to start the plasma-desktop on boot as a service, unfortunately i have had no luck because in the coding there isnt any references that allow this to be run as service. What i did was in CMD/Administrator - I created a service using "sc create Plasmoid binpath= c:\windows\system32\bin\plasma-desktop.exe type= own start=auto" and it succesfully creates the service within windows. The issue is when i go to start in CMD it times out because of service failed code 1053, the service did not start or control request in a timely fashion.

I have found out this is because in microsofts words:

"The ServiceBase class calls the OnStop method directly from the Service command handler that is defined in the ScDispatcherLoop of the Advapi32.dll file. After 30 seconds, if the ScDispatcherLoop thread is not ready to receive a new service command from the service control manager, Windows Service Controller marks the service as "time out." Therefore, you receive this error message." Tried both of microsofts suggestions and still no go. anyone have any suggestions on solving?

I think the problem is that plasma-desktop (on Windows) is an application which displays itself as a full-screen, borderless window between the desktop and the taskbar. It isn't designed to be run as a stand-alone service run at startup (besides the fact that it uses user-specific configs to determine what exactly it will display, and therefore is expected to be run per-user).
If anything, there are a couple of other processes that you may actually want to launch as services. I don't remember off-hand what exactly they're called but I believe one is kinit.exe (or something similar). To find out which processes they are, open the task (process) manager (before you've launched any KDE apps) and switch to the processes tab. Then launch one of the (smaller) KDE apps like kwrite and check which processes spawn.

If you want to launch plasma-desktop on user login, just add a link to it to the (per-user or global) startup directory.

Thanks airdrik, I have taken that into consideration and i have added both the kdeinit and kdecore as services that load during the windows loading screen but the only thing that is stopping KDE desktop from running, aka plasma-desktop, as i understand it is the coding in the file. I have looked into it a bit an worked around the individual profile issue by having it save all the profile data under the default profile loading scheme for all users, i have even gone as far as having the program installed in the system32 folder which seems to cut down some of the program issues i was running into loading it into the default location of program files, and even edited the registry to have it load up under the machine setting replacing the explorer shell so that all i get is the user interface. One of the issues I feel that I am facing is there seems to be some inconsistencies in the coding which create other instances of the plasma-desktop.exe when the toolbars are implemented. Other then that I am stuck between a rock and a hard place because the way it was designed. I understand that other explorer replacements have certain things that is required that was not implimend in this edition of the KDEWin which is required of the shell. I was considering rewriting the program in attempt to cut down the loading times and mimic more of a shell to replace explorer calling on DLL's as modules. If you might have any idea on where to go from there i would be interested to hear what else you have to suggest.

Well, I'm at the end of where I can help, but I will direct you to the kde on windows mailing list, which is fairly active: https://mail.kde.org/mailman/listinfo/kde-windows