Maybe he tried other solution...lol I don't take IR5 support too serious as it's kinda same problem but unique to user slightly every time ...lol RTM + IR5 = 6 months usage with same appearance and usage as activated That it is my motto
I do not have such regkey: HKLM\SOFTWARE\MICROSOFT\RPC\INTERNET I have HKLM\SOFTWARE\MICROSOFT\RPC (no Internet under it). This is vanilla 7x64 SP1 + all updates from Windows update - including optional ones (except language).
Can you check "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Schedule" and see what the value of "Start" is? In some documentation I've seen, if this is not set to 2, then there could be a problem with starting task scheduler.
Ok, i didnt install ioort but i ran the status and i get: LICENSE STATUS: ---OOB_GRACE--- REMAINING GRACE: 4 days (5372 minute(s) before expiring) IORRT is not installed... And the original error is: This copy of microsoft is not activated. You have 3 days left to activate. Ensure you are connected to your corporate neteok to enable automatic activation. Your sys admin can help. Error code: 0x0C004F074
Its a command for rearming XP, but only for 4 times.... & u can use Trilogy to rearm office 2010 (VL editions) edition under XP. Home and student edition isn't VL. VL editions are Standard, Pro Plus & Mondo
Use Office 2010 VL edition with IORRT for infiinite usage with XP See office repository section 2.2.2 then click magnet link It says this in Trilogy details and links
I'm not sure what else you can try but I believe you have some how run into a problem that a few others have with Windows 7. You can try a Google search and you'll find some others are having the same problem as you (task scheduler not starting). Due to this, others are having issues with the disk defragmenter. As a result, I don't believe this is a direct problem with Trilogy (other than the fact that you can't start task scheduler). Sorry I couldn't be of any help to you.
Just curious but is there any mention of any problems within the event viewer regarding task scheduler? If so, it might give an indication as to where to look for an answer. Also, can you run MSCONFIG and ensure that it is set to NORMAL STARTUP (just in case some required programs have been disabled from starting on boot).
It is a normal startup. I did find this in the event log a few times: Code: Task Scheduler service has encountered RPC initialization error in "RpcServerUseProtseq:ncacn_ip_tcp". Additional Data: Error Value: 1721. And also this on every system startup: Code: The description for Event ID 0 from source Schedule cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. I am speechless as this is a vanilla install...
The only other suggestion I have is to uninstall your antivirus (if you have installed one - maybe MSE) and see if task scheduler starts. I have seen postings where AntiVir has caused a similar issue. If that doesn't work, maybe you can try a Window repair or reinstall as a final resort (unless anybody else has any suggestions).
hey timesurfer I have a few questions for you, 1.will this pass windows validation online? 2.if I install windows malicous software removal tool,will trilogy 2.1 be detected as a virus? don't get mad at me for asking these dumb questions i'm sorry if these are dumb questions.
o yea timesurfer in the instructions it says to put in your login information and stuff. wut if i dont have a password for my account?
I think I found it. It seems to be related to a rule on the firewall - I use Agnitum Outpost 7.1 (3415.520.1247). If I assign a rule "block TCP for svchost.exe", Task Scheduler does not start. If I remove this rule, Task Scheduler does not start. A couple of things to note: - I did enable the Rules wizard to see if Task Scheduler makes any connection - this did not turn up anything, so it was safe to assume that it did not. - I did check the firewall logs every time and there are no traces of blocked TCP connections in the logs at all... - I used the process of elimination (of each and every rule defined for svchost.exe) to find the one that causes a problem. Conclusion: - The Task Scheduler service does require TCP - for whatever sinister purpose ;-) - even though it never actually uses it; the service will fail to start. IMHO, this is a serious design flaw. - There are still bugs in Agnitum Outpost 7.1 (3415.520.1247) (some entries are not captured in the log, and network rules are not applied properly). Ok, I will clean up the system now and try to re-run Trilogy... PS. IMHO, this info should be added to the readme...