Tripredacus

I may have noticed that slowdown. I've seen them a few times live, but last time they had a strange lineup. Kirinji - Bluff Spirit from Katamari Damacy

KMFDM - Lund end Eled

A driver before mup.sys causes this. Name the drivers before mup.sys. Real issue can be hardware or software. Which external hardware can you use? USB floppy, USB keyboard, USB mouse Usually I would think it would be whatever is after Mup.sys. Doing a step-by-step confirmation boot would allow you to know exactly which item causes the error.

The link had a wayward period at the end. The board formatted the [ URL ] tag to include this period. I simply did a URL tag wrap on the link and removed the period.

Update chipset drivers for your motherboard to start. I've seen this before but I usually just wait. I know that removable drives aren't indexed. I can imagine this is a pain when doing a lot of disc insertions, but my use of ODs have dropped greatly since starting to use UFDs.

Ok now you can do the next step. Unlike ProcMon, I don't think you can export a bunch of info (you can do one at a time) in order for someone else to look at a log file. So when you open Process Explorer (ProcExp) go to View, Show Lower Pane. When this dot is present (you shouldn't have to use the crosshair anymore), click on the Explorer.exe on the top. In the lower pane it is going to show you all the things that Explorer is doing, such as files, regkeys/paths, handles, mutants, etc. You could try to screenshot the lower pane and post a link to that picture. Also, you should do a test and try dropping the crosshair on some other place on your desktop (the wallpaper where no icon is) and see if ProcExp still says Explorer. It may be that ProcExp can't see that dot like Au3info can?

I have seen this sometimes in the update list, but I just right-click and hide updates that I already have but WU seems to want me to get.

We have another topic that adds things to the context menu, not sure if it will help any...

I would gladly pay you Tuesday for a hamburger today.

Yay Graveworm! I did get to see him solo live once, but I wish I had been around to see him in his prime. Even when I saw him, over 10 years ago? I think so since his latest album at the time was Homebrew 2. Anyways he seemed kinda shakey to me at that show, but I do like his music. Except GTR that is. Not a big fan of that experiment, although the album cover is pretty neat. Burning the Masses - Arms Raised, Eyes Closed

I am reading that WinPE 4.0 has better EFI support than 3.0... also that hardware with UEFI 2.3.1 should have the PXE support, but figuring out what spec boards use for UEFI is pretty difficult.

This is true, the password gets removed, however the number does get used. I've tested with both 1, 3 and 10. I wonder where that value is kept in the OS?

From what I can tell so far, the boot time is "decreased" by moving certain functions to after the desktop shows up. So while full system functionality may take the same amount of time as Windows 7, Windows 8 will appear to boot faster because loading Metro/Desktop is earlier in the order of operations.

There is no harm in creating a second account. He would never end up seeing it unless he did a log-off and saw the welcome screen. Having an extra account can come in handy if the primary account becomes corrupted or has a virus in it or whatever.

I think so. Its is an escape character probably because reg.exe is not smart enough to determine the difference between physical (disk) paths and registry paths.

I can't say about the Account problem, as I never enable the built-in Administrator account. So I have no experience with the OS' behaviour during unattended setup with it enabled. For AutoLogon, I'm not sure why you wouldn't want to use the AutoLogon in Unattend. Presuming you get your account creation thing taken care of, you'll see that it shouldn't be a problem. The only issue you'll run into after that is any user accounts created via Unattend will have their password expire after 2-3 months. Running this in your FirstLogonCommands will fix that: wmic useraccount where "name='AccountName'" set PasswordExpires=false It may also be possible to set AutoLogon using WMI, but I did a quick look in UserAccount with the WMI Object Browser but didn't see it there. Another option may be to write to the appropriate registry values.

Well since you are getting an error, we can start there. When you go into the F8 menu (to choose Safe Mode), choose the Disable Automatic Restart on System Failure. Then when you try to go to Safe Mode and you get the BSOD, it won't reboot automatically and you can tell us what it says.

Well that is OK, if you aren't in a rush then neither am I. Also you can go look in the Task Scheduler to see what it could be. It might show back up because of one of those. Honestly, I never went into there on Win7 until just now and I am surprised how many tasks I have in there.

A lot of the talking points from MS on Win8 are about increased boot time. Tossing around figures and times that remind me of my old Win95 PC as far as boot time. I think I only know one person that shuts down their computer at night. Most people just leave them on since the old days of memory corrupting and PC getting slow are things of the past OS like Win95 or 98.

Enable RDP for Desktop OS: <component name="Microsoft-Windows-TerminalServices-LocalSessionManager" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <fDenyTSConnections>false</fDenyTSConnections> </component> <component name="Networking-MPSSVC-Svc" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <FirewallGroups> <FirewallGroup wcm:action="add" wcm:keyValue="RemoteDesktop"> <Active>true</Active> <Group>Remote Desktop</Group> <Profile>all</Profile> </FirewallGroup> </FirewallGroups> </component> To do on Server 2008 read these: Sample Server Core installation Networking-MPSSVC-Svc on Server 2008 As far as blocking ports, those are inbound ports. So blocking port 21 will stop clients from connecting to FTP software running on the server. Same with port 80 will block others from accessing a webserver. There would be no reason to block those ports if you had those services installed... If you are not running FTP or Web server on your server install, there is nothing to block!

Your logon count is set for 3, which means it will only log on automatically 3 times. Try using a higher number like a million.

Add the user from one PC to a user group on the other PC. As an example. On the HTPC, go into User Groups, add user. Set the user to Computer1\accountname, where Computer1 is the name of the computer you want to grant access to.

I see you posted on another forum, was this fixed yet? Try this driver? http://www.msi.com/service/download/nbdriver-14917.html

That is still not a lot of info, as your google search leads you to believe. This is similar info that can be read of Firefox. So for now, what is the make and model of the notebook? Does it still have the original OS on it or did you format and install your own? Same question about the desktop. You can also use another program (might be better than Au3info now that I think of it.) It is Process Explorer. It also has a little crosshair you can drag over the program. It would then find what process that program is using. Note that it may pick out a Windows service like svchost.exe or another.