Okay, I know most people who come by are going to think "Another person who didn't do his research." i assure you, I have done /more/ than enough research. I have tried every single method I know to fix this problem. So allow me to go into details now.
Before you even mention it, i've ran sfc /scannow until I was blue in the face, assumed ownership of the .dlls and purposely messed them up thinking that sfc might've been infected and wasn't really doing it's proper job - it was, and it fixed my messed up files.
When I attempt to start the service, "Remote Desktop Services" it fails with error #126, which is a common problem right? A quick google will result in many posts about people saying "just run sfc /scannow" elevate it into admin privileges/run it in safe mode. (I've done it all).
So does it work? Nope, everything passes integrity 100%, a lot of the forums will go into further details how a file would be reported bad, but SFC couldn't restore it, so it goes into guides on how to repair the file (doesn't apply to me though)
So on my merry way I go. I systematically go through the services, jack knifing from one dependency to another. Everything that RDC needs to start - works, 'cept the ones that depend on Remote Desktop Services, this mainly being Remote Desktop UserPort Redirect (It fails with a #1068, but that's a given).
So I find several other forums where people talk about dependencies missing in the Remote Desktop Services properties, I check mine? All there, including the notorious Terminal Device Driver.
Again I hit a dead-end, then get annoyed, and start forcefully uninstalling Devices from System Devices, anything with the name "Terminal" doesn't help though. (I put them all back, when my fit finished)
Reluctantly I turn my attention to the only thing I can assume is the problem, and that's the termdd.sys, jumping into this rabbit hole was a good four hour time sink, This being mostly because I couldn't find a single way not even regsvr32 would allow me to "test" if the damn plugin was even working.
So numerous hours later, and tons of batcmd downloads, patches to the registry to try and change the ControlSet, and a ton of other small details that did absolutely nil. I've submitted and posted my problem on the net, hoping /someone/ has had a similar experience or has greater knowledge, and can help me with more troubleshooting, or point me in some direction at least.
I've checked to make sure all the ras*.dll files are in their proper place also, which they are, the termdd.sys is in it's normal location also.
All i'm trying to do is get this damn service to start, but it's turned into a nightmare of 2 days i've thrown into it, any help is appreciated. Thank you in advance.
Oh before I shutup; the computer hardware is
It's an HP, Running Windows 7 Professional 32BIt (SP1) (it's a Point of Sales machine) Updated to the most recent 11/10/2016 (I've even tried pulling The Update KB2667402 (Supposedly it broke a lot of RDC machines)
It only has 2GBS of memory, a 1TB HDD. If you need more specifics than that, just ask.
Before you even mention it, i've ran sfc /scannow until I was blue in the face, assumed ownership of the .dlls and purposely messed them up thinking that sfc might've been infected and wasn't really doing it's proper job - it was, and it fixed my messed up files.
When I attempt to start the service, "Remote Desktop Services" it fails with error #126, which is a common problem right? A quick google will result in many posts about people saying "just run sfc /scannow" elevate it into admin privileges/run it in safe mode. (I've done it all).
So does it work? Nope, everything passes integrity 100%, a lot of the forums will go into further details how a file would be reported bad, but SFC couldn't restore it, so it goes into guides on how to repair the file (doesn't apply to me though)
So on my merry way I go. I systematically go through the services, jack knifing from one dependency to another. Everything that RDC needs to start - works, 'cept the ones that depend on Remote Desktop Services, this mainly being Remote Desktop UserPort Redirect (It fails with a #1068, but that's a given).
So I find several other forums where people talk about dependencies missing in the Remote Desktop Services properties, I check mine? All there, including the notorious Terminal Device Driver.
Again I hit a dead-end, then get annoyed, and start forcefully uninstalling Devices from System Devices, anything with the name "Terminal" doesn't help though. (I put them all back, when my fit finished)
Reluctantly I turn my attention to the only thing I can assume is the problem, and that's the termdd.sys, jumping into this rabbit hole was a good four hour time sink, This being mostly because I couldn't find a single way not even regsvr32 would allow me to "test" if the damn plugin was even working.
So numerous hours later, and tons of batcmd downloads, patches to the registry to try and change the ControlSet, and a ton of other small details that did absolutely nil. I've submitted and posted my problem on the net, hoping /someone/ has had a similar experience or has greater knowledge, and can help me with more troubleshooting, or point me in some direction at least.
I've checked to make sure all the ras*.dll files are in their proper place also, which they are, the termdd.sys is in it's normal location also.
All i'm trying to do is get this damn service to start, but it's turned into a nightmare of 2 days i've thrown into it, any help is appreciated. Thank you in advance.
Oh before I shutup; the computer hardware is
It's an HP, Running Windows 7 Professional 32BIt (SP1) (it's a Point of Sales machine) Updated to the most recent 11/10/2016 (I've even tried pulling The Update KB2667402 (Supposedly it broke a lot of RDC machines)
It only has 2GBS of memory, a 1TB HDD. If you need more specifics than that, just ask.
Facebook
Twitter
Instagram