Install Windows 8 On Socket 478

I have been getting this error ever since switching to Seven, same machines were using Windows XP Remote desktop successfully for years. Just using Seven now.

It does not occur every time I connect to the host from a remote location. At the host machine, the only option is to to click on 'OK.' This brings me back to the same error. Cannot log in, cannot log out. There is no explanation for it. Trying again later doesn't work. Other users cannot log on.

Only way to correct the scenario is restart/reboot/shutdown of the host computer. Is there any resolution to this bug? I have had this problem connecting to vista32 and win7-64 from xp32-sp3. The remote computer should never hang regardless of my misuse. This problem is NOT new, I have tried to resolve it with microoft forums and newsgroups before with no luck. The problem started when I updated to remote desktop connection client 6.0.6001.18000, there were zero problems with the earlier client. People have suggested reverting back to the older version, but hey, you can't.

If you know the update number for the xp remote desktop connection from microsoft update perhaps I can find it and roll it back but I doubt it. Too often these issues are never resolved in these forums and we never hear if the problem was fixed. It's not fixed here.

May 23, 2014. How to install Windows 8 to PC with Intel Celeron, CPU - 2.13GHz, Code name - Prescott, Socket- 478 mPGA. Instructions - MMX, SSE(1,2,3)? After the installation displays an error 0x0000005D.

I'm not willing to go through all the diagnostic steps you have listed. If the connection can work once, it should work multiple times. It always hangs up on the first reconnection attempt. Edit: isn't it a little insidious that microsoft employees are going through these posts and marking them answered? Only the original poster should be able to decide if they are answered. I do not see where you are giving any info. To help you here.

You need to tell us what OS is running on the remote PC's I use RDP very liilte but have no problems when I do. I can use it between XP pro and win 7 without any lockup at all. I can also use it with a old term. Server without lockup. I just connected and disconnected three times within seconds and it worked fine. Unless you are willing to do what is asked of you in these forums, you are not going to get help. So stop whining about what worked before and provide some info. Hype Mac Keygen more.

So we can try to help. The required diagnostic information is the following: 'The task you are trying to do can't be completed because remote desktop services is currently busy. Please try again in a few minutes. Other users should still be able to log on.' Someone in programming at microsoft should be able to go to the code that produced this error message, examine it, and report back with an explanation on why the program shows it.

If I just had that much information, a fix might be possible at some point. I just tested this a bit more, and there is not a similar bug when the remote is win 2003 server. As I said above, vista32 also has the problem, but with a different error message as I recall. It was with a remote vista host that I first noticed the problem after the remote desktop connection client update. I could connect to vista ok using the earlier client. It's strange there are only a couple of hits on google for this problem, this thread being one of them. Bing has no hits for it at all.

Redeyedog, you have been asked to do a clean boot and test.your answer was 'It has been ignored in the normal manner today's 'support' techs do asking us to take those 'idiot steps' which have been pushed on us for over thirty years by Microsoft whenever there is a problem they do not know how to fix! ' That is whining / refusing to do YOUR part.' If you think doing a clean boot to test is 'idiot steps' I really do not see you can be help, as that is trouble shooting 101. And Paul has stated it works with his 2003 server.you have not told us what version of the server you connecting to.

It works with mine, it works for others, so IT WORKS. Now that you see it does work for others MAYBE you can back off and do as you are asked, without you doing your part it will be very hard for anyone to help you find YOUR issue. I have to get this working.

I've done the clean boot, with zone alarm truevector service disabled as well. The bug is still there, but in possibly a slightly different form. The reconnect always hangs, to the point where the box has to be hard reset to get back in.

But the error message 'The task you are trying.' Is gone -- I just get the blue graphics with the spinning circle thing. This needs to be escalated at microsoft's side. I will post back here if I can get this fixed. Please let me know if you fix it also. We may have to support ourselves on this.

There is no point ranting at microsoft. They are totally inured to this approach. How can we get this bubbapcguy to go away? Attempt to login to the machine interactively at the local console. I just replied in the other thread you provided a link to. I have not seen this 'The task you are trying to do can't be completed.' Error popup in over 6 weeks or so, and can't take the time to try and reproduce it.

It may or may not have something to do with zone alarm. Microsoft won't say anything about it since they don't live here anymore, at least not in any valuable technical capacity. In my reply on the other thread I confirm the bug with zone alarm and remote desktop. The remote host hang is mentioned in the official zone alarm release notes, so I'm not making this stuff up. You must be seeing this error by means of an entirely different pathway not related to zone alarm. Shiro Can We Talk Rarest.

In my case, zone alarm might be exposing a weakness in the microsoft code or vice versa. I am having this same problem and I have ZA installed. I thought I would post so that bubbapcguy might realize that it is a lot more than two people having this problem.

I am tired of these posts getting closed as answered as well. I have quite a few problems with Windows 7 that are all over the forums but Microsoft seems to not want to do anything about them. They all get closed as answered because we should reinstall windows 7 and then not install anything on it or try and use it with our current network setup. I too had the same problem when trying to log back in to my Windows 7 x64-bit pc after using remote desktop through a eee pc 1000 laptop (which has Xandors OS installed.) So once I had ended my session through the eee pc laptop, I would go back to my Windows 7 x64-bit desktop pc and try to log in but it would just hang at the welcome screen with the pointer going in circles. Issue went away once I uninstalled Zone Alarm free edition (using windows built in firewall now). I also uninstalled SuperAnti Spyware free edition just for the heck of it.

Kuddos to Paul and Redeye dog for believing and keeping this alive. I am not sure if it helps I am a server admin in my company, i found that if you uncheck the tick boxes both Printers Clipboard transfer & Printers in Remote Desktop Connection It might avoid the issue you are having Exact instruction: Open Remote Desktop Connection dialogue ->Under Local Resources Tab ->uncheck Printers & Clipboard tick boxes Hope this helps My guess is remote desktop takes to long to map your printer drivers to remote server / workstation, however it took too long to do so and got timeout Thats why you got that error message Just my guess!~~. My server 2008 R2 Farm has been up and running for many months with no issues at all, until last week, and suddenly several users keep getting that same error. Unlike what others have reported though, my users are on Thin Clients not running XP or Win 7. By going through the event logs, I was able to find entries mentioning errors unloading things from the registry and it names the specific process ID's, and I do find those running.

Once I kill those specific process ID's, the user can then log in. I am baffled as to what could be suddenly causing this. The previously mentioned hotfix is not applicable as it is included in the latest SP which is applied. Please post details if anyone has any ideas Ron GIllis. I'm having this same problem all of a sudden on a Windows 7 Ultimate SP1 client.

The client has no 3rd party firewall software installed, and is NAT'd properly. When I attempt to establish a terminal services connection to it, I am getting either of these messages: 1. This computer can't connect to the remote computer. The two computers couldn't connect in the amount of time allotted.

Try connecting again. If the problem continues, contact your network administrator or technical support. The task you are trying to do can't be completed because remote desktop services is currently busy. Please try again in a few minutes. Other users should still be able to log on. This client has worked perfectly fine for the past year — can a Microsoft developer please look at this bug and investigate its cause? Please let me know what debugging tools I can use to gather more information, to help isolate the bug to the correct library or device driver.

If this post was helpful, please click the little 'Vote as Helpful' button:) Trevor Sullivan. I just had a whole string of these messages. I had a remote desktop session open to a 2008 R2 server from a Windows 7 64-bit desktop, but minimized.

The remote server is being backed up over the network. Expand the remote desktop window to check on backup progress. The remote desktop window is solid black, and stays that way.

Tried closing the window and reconnecting. Got the 'currently busy, please try again' message. Try again, fails. Try again, fails. Look up the error, find this thread.

Try again, fails. Try again, fails. Finally after doing this for several minutes the remote desktop finally appears., So basically if the remote server is busy doing something else, remote desktop gives up trying to connect almost instantly and doesn't wait around for the remote server to not be busy. This looks like a bug. It should wait a reasonable amount of time for the remote session to establish on a busy server, like 30 to 90 seconds.

Not 1.5 seconds. Otherwise the result is that a hung remote server that is at constant high load may never let the remote administrator connect, because of the near-instant connect-timeout. @ds5384: The rare times that it does happen to me, it's usually because of a failed logon attempt, or a session that gets disconnected unexpectedly. Next time that someone has this problem on an important system, they should push for Premier Support to investigate and publish a public hotfix. There's no reason that a failed logon session should hang the Terminal Services service indefinitely. Unfortunately the last time I experienced it, it was on my system at home, which doesn't exactly warrant a call to Premier Support.

If this post was helpful, please click the little 'Vote as Helpful' button:) Trevor Sullivan. This happened to me today for the first time since I installed Windows 7 Enterprise at work.

I usually work remotely over RDP from another Windows 7 machine. Today I came into office and logged on locally, but got black screen after entering password.

I tried to log on over RDP but got this error. No I have no way to finish my work, save documents and stuff.

Good job, Microsoft. Keeping good traditions. PS: System is absolutely clean, no alien drivers or software is installed. Everything I work with does not require administrative rights. Very proud of you, Paul!

Good job and well done! Now - as far as the Microsoft Tech guys, you sort of at least have to respect their attemt to help out.:) I agree they are quick to resolve a questions without the concent of the one who posted the question initially.

This is what's really disapointing. We're here to help eachother. Let's make us better, our environments better, and why not - the Microsoft tech even better. Next time they'll know it better. Thanks Paul for all your dedication into addressing this issue. This is not fixed, by the KB patch or by any other means listed.

From what I can tell in my stance what happens is this: 1. Users enter credentials 2. System starts loading profile 3.

User is booted back to login screen and has to enter credentials again 4. Error occurs asking them to retry later. This is a joke. Microsoft should stop wasting thier time making cosmetic changes to thier image, and thier software and work on the underlying technology that makes things work. Its seriously a joke.

There is so many people complaining about this issue online - you would think they would fix this rubbish. We just now had this same problem for one of our clients. Users were able to login but everything was extremely slow. After some time other users could not login and got the RDS message. On top of the error message those who were already in a session could not open any Office products (MS Word) because it would hang. I tried restarting the spooler and it would fail.

I then ran a script and it seemed to have solved our issue for the time being. Users can now login without the error message and open apps without any issues.

Dim objFSO, objFolder Set objFSO = CreateObject('Scripting.FileSystemObject') Set objShell = CreateObject('WScript.Shell') If objFSO.FolderExists('C: Windows system32 spool PRINTERS') Then Set objFolder = objFSO.GetFolder('C: Windows system32 spool PRINTERS') If objFolder.Files.Count = 0 And objFolder.SubFolders.Count = 0 Then objShell.Run 'Net Stop Spooler', 0, True objShell.Run 'Net Start Spooler', 0, True Else End If End If.

Since this site won't let me respond with an answer, I can only add this comment here: It is possible to bypass all the CPU checks to install and boot Windows 10 on an unsupported CPU. It is definitely not recommended, but if you are one of the crazy people like me, you can use the same method as Win8 to remove the CPU checks. Download Win8 no NX installation kit 2.

Make a new partition for Win10 3. Extract the sources install.wim file 4.ran out of characters. Source: – Aug 31 '16 at 4:43. The only solution is to get a newer laptop. Background: The pentium IV CPU is very old.

Newer CPU has gained new features. One of those is the NX bit which is used to enhance security. Windows 7 can optionally use this. Windows 8 and later require it.

So to install windows 10 you need a CPU with this hardware part in the CPU. And as far as I know there are no CPU's which support NX which fit in a P IV socket.

Update and some relevant info: • •. Important to notice: Old P4's (Willamette core from about 2000 and Northwood cores from 2002) simply do not have the NX bit. More recent P4's (Presscott core from 2004-ish and later) do. If your CPU is new enough and you have a BIOS which supports it then you might be able to run windows 10 after all. • Here is (in other words, it might run the OS if you patch something)) • Power usage: P4 were notoriously power hungry. Depending on where you live it might make economic sense to dump the old P4 and replace it with something less power hungry. This also depends on which P4 you have.

One solution could be to try to upgrade the CPU itself. Since you did not give the exact model (ASUS 2000 returns nothing), it's hard to tell if it is possible to do it, but it might. You would have to find out what the socket is, and try to get a second hand Pentium 4 with the NX bit, or even a Core Solo/Core Duo, Core 2 Duo. A BIOS upgrade might be necessary.

(On one of my laptops it was possible to upgrade the CPU from a Celeron M to a Core Duo with the NX bit. Those things come fairly cheap.).