So I've got an impressive little problem - I boot up my computer this morning, and out of the blue it's giving me System Error's that state:"The program can't start because SspiCli.dll is missing from you computer. Try reinstalling the program to fix this problem." It seems to have disabled every 32-bit app that I have . . . I'm able to get online w/ Explorer-64, and my 64-bit version of Media Player Classic is still working.And no matter how far and wide I search, I can't seem to find anyone who's ever had this problem before. I didn't install or uninstall any new software in the past 2 days, but I did trya System Restore back to several different points with no luck. And for what it's worth, the sspicli.dll is physically there in the windows\system32\ directory, as are all the libraries it's linked toas referenced here: http://www.win7dll.info/sspicli_dll.html I ran a full scan with MS Security Essentials - found a couple trojans, but nothing that fixed the problem. I would tryregistry scan/fixing software . . . but alas,I get the same error when trying to install any new software.Anyone have a solution? I'm pretty handi-capped rig right now, andI'd hate to have to reinstall Win7 - especially without knowing what caused the problem.Oh, and one other thing that may or may not be related, the computer no longer is able to restart . . . e.g. if I hit "restart" from the Start menu, it'll shut down, but then sit paralyzed without re-booting. Doesn't post in BIOS, or even output anything to the monitor. I hear the cooling fan(s) ramp up and turn off every 2-3 seconds.

Wellone that intriqued me is that you used a program called CleanMyPC which I'm very willing to bet is the cause of your problems which you mentioned here http://www.win7heads.com/windows-7-miscellaneous/25752-sspicli-dll-missing.html. Registry Cleaners will (in my opinon) cause more problems than they solve. Its just like the guy said about what his problem wsa when he stated this quote: It seems as though editing the registry causes problems.When you use a registry optimizer, fixer, and/or cleaner before rebooting after installing an important Windows 7 update, this happens.I've tried to locate my problem and I think this was it. MCSE, MCSA, MCDST

Wellone that intriqued me is that you used a program called CleanMyPC which I'm very willing to bet is the cause of your problems which you mentioned here http://www.win7heads.com/windows-7-miscellaneous/25752-sspicli-dll-missing.html. Registry Cleaners will (in my opinon) cause more problems than they solve. Its just like the guy said about what his problem wsa when he stated this quote: It seems as though editing the registry causes problems.When you use a registry optimizer, fixer, and/or cleaner before rebooting after installing an important Windows 7 update, this happens.I've tried to locate my problem and I think this was it. MCSE, MCSA, MCDST It's possible - but I haven't done anything with that program (or the registry as a whole) since I last posted about it 2 weeks ago. I was able to restore an older (good) version of my registry through DOS prompt, and then found that the version of CleanMyPC I had wasn't Win7 compliant. Upgraded to 4.2X and it seemed to work, but haven't touched it since. :shrug:Regardless, I'm pretty stuck right here. I chatted for a few minutes w/ Microsoft tech support, who could only suggest that I do an in place upgrade using my Win7 DVD. But even that doesn't work . .. it gets to the "gathering system files & info blah blah" stage and shuts down with a generic error - I'd say it's running into the same missing .dll error that all my other apps are hitting.A clean upgrade/install would probably do the trick, but I'm hesitant to resort to that without knowing what's actually wrong.

Why not try that process again to reproduce the error so this time you note it and report it to us, it might help. I'd be curious to know what the genreric error is that wouldn't allow the upgrade.MCSE, MCSA, MCDST

I believe you can boot the DVD and still do an inplace upgrade. You don't have to do this from a running OS.Rich

You know it's in system32 but did you see if it was here:C:\Windows\SysWOW64Seasons greetings!

You know it's in system32 but did you see if it was here:C:\Windows\SysWOW64 Seasons greetings! Ah, I didn't know it was supposed to reside there as well. So it's not there - but there is a sspicl).dll file . . . which I'm assuming is the file I'm looking for, erroneously renamed somehow. I've taken ownership of the directory so I canchange it back, but I'm now getting the following error -Error 0x80070570: The file or directory is corrupted and unreadable. I see some people have recommended startup repair as way to solve this - or should a chkdsk be my next step? Or am Imissing something in setting up permissions? I'm very new to the Vista/7 way of file security - permissions, ownership, etc.Suggestions?

Why not try that process again to reproduce the error so this time you note it and report it to us, it might help. I'd be curious to know what the genreric error is that wouldn't allow the upgrade. If I get to it again I'll write it down - but the gist of it was: "Windows 7 install can't continue, try rebooting."

If you can still get to the 7 desktop open an elevatedcommand promt and enter "SFC /SCANNOW" (system file integrity check / repair). SFC /SCANNOWSeasons greetings!

I believe you can boot the DVD and still do an inplace upgrade. You don't have to do this from a running OS. Rich Just tried it out, won't let you do an in place upgrade from boot - you have to be in an OS.

If you can still get to the 7 desktop open an elevatedcommand promt and enter "SFC /SCANNOW" (system file integrity check / repair). Thanks for the reply - before I saw it I ran startup repair from the Win7 DVD. While it fixed the apparent problem (recovering the SspiCli.dll file), I had constant BSOD's. All different causes - ntfs.sys, win32.sys, bad pool header, memory management, etc., etc. And it still wouldn't let me do an inplace upgrade to refresh the OS install. Came up with the useless error every time - something about not being able to copy files, try rebooting and running install again. So I've thrown in the towel, re-formatted the drive, and installed Win7 from scratch again. *sigh* Been an hour or so up on the new OS install, going through the painstaking process of reinstalling all my apps, bookmarks, files, etc. So thanks for the help everyone, I'll update if there any more developments, but hopefully not. This is the 7th or 8th computer I've built for myself, and I've never had this many problems before - hopefully I've seen the last of them.

If you are not yet familiar with the back up and restore utility, after you are set up please browse the built in help and support and take alittle time to create a"systemimage" - a copy of the Windows partitionwhich you can use to restore your computer along with all of your installed programs and personal settings in just a few minutes.Seasons greetings!

If you are not yet familiar with the back up and restore utility, after you are set up please browse the built in help and support and take a little time to create a "system image" - a copy of the Windows partition which you can use to restore your computer along with all of your installed programs and personal settings in just a few minutes. Seasons greetings! If I can ever get things running stable enough to bother backing up, I'll be sure to do so. Having tons more BSOD issues now - memtest86+ showed a bunch of errors, but in trying to narrow down whether it's a DIMM slot or a ram stick I can't seem to reproduce them - even in the original configuration. Aggravating.

Do remember that malware and registry cleaners both can cause this error to your system. To fix "sspicli.dll is missing", you just need to download a new sspicli.dll and save it to its default path. The path for 32-bit systems (x86 machines): %SYSTEMROOT%\WINDOWS\System32\ The path for 64-bit systems (x64 machines): %SYSTEMROOT%\WINDOWS\SysWOW64\ For more information about sspicli.dll, please see http://www.dllsuite.com/Windllresult.aspx?keyword=sspicli.dll

I had the same problem after restoring the computer to an earlier point. (Two days back) After the system restore the SSpicli.dll missing error comes up. The file is located in the System32, tho not in the system64. If you copy the one in the 32 folder to the 64 folder you will get a different error when you try and run your programs. What worked for me was the following: Click windows icon, under search type in run hit enter, then in the run window enter SFC /SCANNOW, let the scan run it's full course. (Note first two times I entered it the dos screen just popped up and closed almost immediately after, on the third time it stayed open and you could watch the progress, took about 5min to complete.) After the scan is done, then copy the sspicli.dll to the syswow64 folder and restart the computer. I used the restart button in windows. That fixed the problem for me. The only other note is when I first opened the programs that were causing the errors it took longer for them to open, the pause was long enough to think the program was going to crash, tho lo and behold they all opend just fine. The delay only happened the first time and now when I run the programs, they all open at the normal speed. If you don't have a SSpicli.dll on your computer at all, you can download it to another computer. I couldn't run internet explorer and luckily had the file in the 32 folder. Hope that helps someone else out. It mainly may have been simply running the SFC /SCANNOW and then copying the file and then restarting that did it. Without restarting my system didn't apply the fix. As stated above the two locations the file shoud be in are: The path for 32-bit systems (x86 machines): %SYSTEMROOT%\WINDOWS\System32\ The path for 64-bit systems (x64 machines): %SYSTEMROOT%\WINDOWS\SysWOW64\ Anyone know why no spell check exists in the posts? Matbe things like %SYSTEMROOT%\WINDOWS\SysWOW64\ would cause trouble? =`)