allen2

As the csrss crash might be coming from intelppm.sys, it could be that the processor was too hot because it was also running at 3.5Ghz most likely you have overclocked it. I would avoid overclocking it for the time being and see this happen again.

You could try autoruns.

On windows 2008R2, default security settings will already log in the eventlogs what you need.

Did you tried this one or this one?

In nlite not to my knowledge, but you can edit the unattended.txt and add "DriverSigningPolicy = Ignore" in the [unattended] section as explained there.

Is icaLCs a new command or a mistake ? The right one is icaCLs.

The takeown command should be run before the icacls one.

A lot are. For the others installrite should be enough as it is able to monitor registry entries and files modified.

Right click on services on the left pane, and select "export list".

You could try regshot (if your tweak/configuration settings are stored in registry) or installrite: - You'll need prepare a clean windows install - launch regshot or/and installrite and do their first shot - then configure and tweak you install to your liking - take the second shot and do the comparison. Regshot will need that you do the rest of the job and installrite will do it for you.

Just to satisfy my curiosity, how much space do you gain by compressing already compressed updates (please post the total space used by updates before and after) ?

The right syntax for "start" is at least to give a title and an executable. START /WAIT Dir\"%%~nA"\KB123456.exe /quiet /norestart should be START "hotfix" /WAIT "Dir\%%~nA\KB123456.exe" /quiet /norestart and i put "hotfix" you can put almost whatever you want. I also set the right quoting method in this case. Lastly, i don't understand why you would get a folder named like Windows*-KB* (that's what you do when using "\%%~nA\ ") as in the batch you pasted, all hotfixes must be in the same folder....

It could be that the usb mode is set to 1 (so 10Mb/s) in bios or usb2 isn't even supported on your motherboard.

Yes and yes if you do it properly.

Yzöwl was right: in this case if the hotfixes contains space in their name, the quotes are required (and won't cause any trouble). And that's why he put them.

Usually, it isn't the login script being too fast but the computer boot which allow the user to open the session before all network layers are up.

It might not exactly be your request but bginfo can report free space on the desktop background and not in the taskbar.

Variable with space might be used without quote in some and never in other: - when using a variable with space after echo, you don't need quote whatever the variable with space (of course if the variable doesn't contain other special characters). - when using a variable with space after if (for testing), in most cases you'll need to have it quoted the only exception is the syntax "if defined".

The main thing there is finding out what you consider slow (special application ? special operation with special application ? everything ?). In most case you can solve those speed problems by either buying only one or two component and if you aren't doing cpu intensive calculus like encoding video, more cpu isn't going to help. As a side note, having more cpu and/ or hyperthreading might slow down some apps.

I wouldn't use Jaclaz method as it might be dangerous if the ini file contains entries that are already environment variables and might cause some strange behavior is the script doesn't end: [Directory] Path= USERNAME= @Geej I did add the double quote on purpose to be able to use properly the variable after.

Try launching it with something like this: start "wizmo" /separate wizmo.exe play=theme.wav

Try this: Set inifile=folderstore.ini Set txt1=%~n011.txt rem :: Note: Current script unable to work with space FOR /F "delims== tokens=2* usebackq" %%i in (`type %inifile% ^| find "Cabfolder1="`) do (set value1="%%i") if %value1%=="" (color 1A && echo Folder path not defined.) else (Echo %value1%) echo. pause

Or disable the associated network card.

I don't understand a thing of what you're trying to achieve when you explain it like this (but perhaps it is only me). Could you explain a little more or make a drawing ?

Sorry to disagree there but Microsoft didn't release for enterprise only. Also the OP is implementing its solution for his enterprise so what's wrong there ? And of course the reg entries (for wsus) should be removed after installing all updates. And just for the record, those reg entries don't block windows update access using IE and that's what most people use to update their computer (when not in an enterprise).