Does anyone know what would happen if you took a brand new Windows 7 Pro OS and after installing all critical updates and setting up all customizations, a person used EFS (Encrypting File System) and encrypted core system files? I've read about Windows File Protection (WFP) which prevents programs from replacing critical Windows system files, but  this tool depends on the files sitting in a cache. So why not encrypt the system files as an alternative. 

*In this scenario I'm only thinking of a single user who still has access to the internet. 

Can someone help me decipher my Crash Dumps?  I need to isolate the specific problem... I can't tell if it is the USB controller itself, its associated drivers, or the wireless USB device connected to the controller.

According to the information I have, it seems to be related to the VIA chipset drivers.  I've updated everything, and did all Windows Updates.  CHKDSK & Windows Memory tester says everything is OK.

WhoCrashed lists xhcdrv.sys (VIA eXtensible Host Controller) as the problem.  On the other hand, WinDbg says it's an NT-related module.  Neither one lists my wireless adapter as the culprit.

Error types:  DRIVER_CORRUPTED_EXPOOL, DRIVER_IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA.

---I can provide the crash dumps as soon as they verify my account --- It will not let me post my OneDrive link until then---

Windows 7 x64-bit with SP1 // Gigabyte GA-Z77X-D3H // CORE I7-3770K

Thanks in advance.

I disable the wake timer in windows power options, using admin rights. It stays disabled for some time (a couple of days) and then it is enabled by itself.

I need to disable it, besause it leads to errors when resuming from sleep.

i want to edit context menu of windows Explorer. and i want to create my own menu with sub menu as shown in image. and also do some task like copy and move to other destination.

Can any one please show me how to do this with registry.

Is this possible or not? if it is possible please give me step by step answer.

Folder/file -->Right click-->List of menu(Open,copy,send to,My menu name)-->My menu name ->(Copy,Move) -->copy -->list of"fix" folders or destination names(They are already in my Harddisk) (On click on it it will perform copy operation).

How do you get a copy of the Fixit for me report?http://support.microsoft.com/gp/windows-update-issues

Obviously you can print screen but is there a better way?

TIA, Gerry

An error occured while checking for new updates from my laptop

WindowsUpdate_80072EFD" "WindowsUpdate_dt000

WindowsUpdate_80244018" "WindowsUpdate_dt000

Help me with this error. i try to solve by using Microsoft TechNet but still cannot solve the problem, Also i try all the link that appear still cannot solve. Help me please..

Hello everyone!

I have a serious problems with my laptop. My windows (W7 Ultimate 64 bit) keeps crashing with BSOD and only thing i understand is that it is caused by tcpip.sys . Sometimes it occures minute after windows turns on, sometimes after half hour and sometimes after few hours. It does not depend on what I am running, it crashes when i am on Mozilla Firefox, Excel, MSAccess etc. or basically when I am doing nothing.

I got a lot of malwares and viruses in past month, so first i did system recover, and than i upgraded my AVAST! Free to Internet Security, and installed Malwarebytes Anti-malware Pro. In that period first crash occured, duo to malwares/viruses (i red on a forum that this scum can be responsible for tcpip.sys BSOD) or newly installed softwares (Avast or Anti-malware, i red that often protection softwares cause these kind of system malfunction) or system recover or something fourth, i don't know. So after i had removed all viruses and malwares from my HDD, I had uninstalled AVAST! and Anti-malware using REVO uninstaller, but the crashes persisted so I installed them again (I haven't tried to uninstall them using their special uninstall programs such as avastclear.exe because there are no evidence in dump files, as far as I can tell, that these softwares are responsible). Also I updated my wireless driver, it didn't solve the problem. 

It irritates me greatly, crash occured twice while i was writing this post so I would much appreciate any help.

There are 4 dump files on https://onedrive.live.com/#cid=243D3C3DF3800180&id=243D3C3DF3800180!107

Some of X550CC specs, if needed I will provide more:

CPU: Intel® Core™ i5 3337U Processor

Chipset:  Intel® HM76 Chipset

Grapich: NVIDIA® GeForce® GT 720M and Intel(R) HD Graphics 4000

Networking: Integrated 802.11 b/g/n; Built-in Bluetooth™ V4.0; 10/100/1000 Base T

Wireless and driver: Atheros AR9485WB-EG Wireless Network Adapter  v. 9.2.0.504

We're having random BSOD's from our computers.  Only user dump files are created.  Here's a snippet of the file, I'm wondering if anyone has any ideas what might be the cause?

PROCESS_NAME:  csrss.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  00000000027be0b8
READ_ADDRESS:  00000000027be0b8
FOLLOWUP_IP:
sxs!BufferedStream::getLineBuf+1f
000007fe`fcc41b2f 410fb702        movzx   eax,word ptr [r10]
NTGLOBALFLAG:  0
APPLICATION_VERIFIER_FLAGS:  0
APP:  csrss.exe
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
FAULTING_THREAD:  0000000000001170
BUGCHECK_STR:  APPLICATION_FAULT_INVALID_POINTER_READ_STACK_POINTER_MISMATCH
PRIMARY_PROBLEM_CLASS:  INVALID_POINTER_READ_STACK_POINTER_MISMATCH
DEFAULT_BUCKET_ID:  INVALID_POINTER_READ_STACK_POINTER_MISMATCH
LAST_CONTROL_TRANSFER:  from 000007fefcc41aea to 000007fefcc41b2f

SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  sxs!BufferedStream::getLineBuf+1f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: sxs
IMAGE_NAME:  sxs.dll
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7c9cc
FAILURE_BUCKET_ID:  INVALID_POINTER_READ_STACK_POINTER_MISMATCH_c0000005_sxs.dll!BufferedStream::getLineBuf
BUCKET_ID:  X64_APPLICATION_FAULT_INVALID_POINTER_READ_STACK_POINTER_MISMATCH_sxs!BufferedStream::getLineBuf+1f
ANALYSIS_SOURCE:  UM
FAILURE_ID_HASH_STRING:  um:invalid_pointer_read_stack_pointer_mismatch_c0000005_sxs.dll!bufferedstream::getlinebuf
FAILURE_ID_HASH:  {558625b4-41c0-b4dc-930c-c09d8e328e35}

My TOSH laptop wont sleep (again).

I have it configured to share files across networks, either as the sharer or sharee.  I have found several descriptions of "allow sleep with remotes open (for example: http://iboyd.net/index.php/2010/05/16/windows-7-power-management-fixing-pc-insomnia/) and my registry is configured to show the option on power configuration.

The option to allow sleep with remotes open is YES

Computer management shows NO shares active.

Yet I get "An active remote client has recently sent requests to this computer." when I do

powercfg -requests

The power schemes in Win 7 leave a lot to  be desired.  Like this (hidden features that require considerable searching, then do not reliably work) as well as the fact that my display brightness on battery keeps getting changed to FULL without me doing anything.

So what am I doing wrong?

I have one Windows 7 computer that is somewhat randomly dropping the remote connection.  I set the Keep Alive packet to 1 and restarted, but the user just lost the connection again while typing after being logged in for about 3 minutes.

I have 5 other Win7 remote desktops whose users are not reporting this problem. All of the remote desktop computers are getting the same group policies. I also have some 2008 R2 terminal servers with no reports of this problem from the 100 or so users who connect to them.  The same user with the Win7 problem connection is not having any problem with connections to the terminal servers, so I don't think it's a problem with his local office pc.

I'm going to try changing to a different switch port, but I'd like to hear other suggestions if anyone has them. Thanks.

- System 

  - Provider 

   [ Name]  Microsoft-Windows-Kernel-Power 
   [ Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4} 
 
   EventID 41 
 
   Version 2 
 
   Level 1 
 
   Task 63 
 
   Opcode 0 
 
   Keywords 0x8000000000000002 
 
  - TimeCreated 

   [ SystemTime]  2014-03-06T22:00:25.156250000Z 
 
   EventRecordID 76624 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  4 
   [ ThreadID]  8 
 
   Channel System 
 
   Computer TEST-TENCENT 
 
  - Security 

   [ UserID]  S-1-5-18 
 

- EventData 

  BugcheckCode 0 
  BugcheckParameter1 0x0 
  BugcheckParameter2 0x0 
  BugcheckParameter3 0x0 
  BugcheckParameter4 0x0 
  SleepInProgress false 
  PowerButtonTimestamp 0 
what's that above saying?
Xen HVM windows vm.

A close friend's machine was blue screening on boot so he had me take a look at it.  The error in the BSOD indicated Windows was having trouble reading from the drive.  Although the drive wasn't clicking, based on what I was seeing, it seemed pretty clear the drive was on its way out.  I ran chkdsk, several times, and it found plenty of bad sectors but wasn't able to really fix anything.  Fortunately I was able to

• clone the drive using gparted
• run chkdsk
• fix the master boot record, boot sector and boot configuration data store
• run chkdsk again
• Now all is well

Upon booting I noticed the system was dreadfully out of date: Firefox, Java, Reader, Flash - the works - so I updated all that.  I also noticed it was missing something like 50-70  Windows updates so I had to straight that right away.  It managed to install 15-20 before failing with 80070057.  This to me isn't too uncommon so I rebooted thinking it wouldn't choke next time. Much to my chagrin, any subsequent attempts fail with error 80070057.  I even tried installing just a few updates at a time, even just 1, and the error persists.  My assumption is that one or more files are maybe damaged and need to be fixed.

I ran sfc /scannow and it gets to about 27%, then fails with "Windows Resource Protection could not perform the requested operation."  I did the following:

• backed up the existing CBS log
• ran sfc /scannow again
• watched the log in powershell via Get-Content C:\Windows\Logs\CBS\CBS.log -Wait

It started out strong

PS C:\Windows\Logs\CBS> Get-Content C:\Windows\Logs\CBS\CBS.log -Wait
2014-03-06 18:48:33, Info                  CBS    Loaded Servicing Stack v6.0.6002.18005 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6
002.18005_none_676975d87cc9b6e6\cbscore.dll
2014-03-06 18:48:33, Info                  CSI    00000001@2014/3/6:23:48:33.027 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef0cf8c85 @0x7feff3f53ae @0x7feff3c3ed1
 @0xffa949a8 @0xffa930c9 @0xffa93578)
2014-03-06 18:48:33, Info                  CSI    00000002@2014/3/6:23:48:33.045 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef0cf8c85 @0x7feff4386cf @0x7feff4125d9
 @0x7feff3c3feb @0xffa949a8 @0xffa930c9)
2014-03-06 18:48:33, Info                  CSI    00000003@2014/3/6:23:48:33.048 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef0cf8c85 @0x7feff21838d @0x7feff2184ba
 @0xffa94207 @0xffa93125 @0xffa93578)
2014-03-06 18:48:33, Info                  CBS    NonStart: Checking to ensure startup processing was not required.
2014-03-06 18:48:33, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDispo
sition = @0xb8fad0
2014-03-06 18:48:33, Info                  CBS    NonStart: Success, startup processing not required as expected.
2014-03-06 18:48:33, Info                  CSI    00000005 CSI Store 4751600 (0x00000000004880f0) initialized
2014-03-06 18:48:38, Info                  CSI    00000006 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:38, Info                  CSI    00000007 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:39, Info                  CSI    00000008 Repair results created:
POQ 0 starts:

POQ 0 ends.
2014-03-06 18:48:39, Info                  CSI    00000009 [SR] Verify complete
2014-03-06 18:48:39, Info                  CSI    0000000a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:39, Info                  CSI    0000000b [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:40, Info                  CSI    0000000c Repair results created:
POQ 1 starts:

POQ 1 ends.
2014-03-06 18:48:40, Info                  CSI    0000000d [SR] Verify complete
2014-03-06 18:48:40, Info                  CSI    0000000e [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:40, Info                  CSI    0000000f [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:41, Info                  CSI    00000010 Repair results created:
POQ 2 starts:

POQ 2 ends.
2014-03-06 18:48:41, Info                  CSI    00000011 [SR] Verify complete
2014-03-06 18:48:41, Info                  CSI    00000012 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:41, Info                  CSI    00000013 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:41, Info                  CSI    00000014 Repair results created:
POQ 3 starts:
..... and so on

Until it hit a problem

POQ 34 ends.
2014-03-06 18:49:08, Info                  CSI    00000091 [SR] Verify complete
2014-03-06 18:49:08, Info                  CSI    00000092 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:08, Info                  CSI    00000093 [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:09, Info                  CSI    00000094 Repair results created:
POQ 35 starts:

POQ 35 ends.
2014-03-06 18:49:09, Info                  CSI    00000095 [SR] Verify complete
2014-03-06 18:49:09, Info                  CSI    00000096 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:09, Info                  CSI    00000097 [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:10, Info                  CSI    00000098 Repair results created:
POQ 36 starts:

POQ 36 ends.
2014-03-06 18:49:10, Info                  CSI    00000099 [SR] Verify complete
2014-03-06 18:49:11, Info                  CSI    0000009a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:11, Info                  CSI    0000009b [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:12, Error                 CSI    0000009c@2014/3/6:23:49:12.802 (F) d:\longhorn\base\wcp\primitiveinstallers\filehierarchy.cpp(1939): Error STATUS_INVALID_PARAMETER originated in fun
ction FileInstaller::CFileInstallerHierarchy::PortFileInformationBetweenCdfs expression: TmpBlob.Length == sizeof(LUACDF_FILE_ENTRY)
[gle=0x80004005]
2014-03-06 18:49:16, Error                 CSI    0000009d (F) STATUS_INVALID_PARAMETER #2119209# from CFileInstaller::CommitChanges(...)[gle=0xd000000d]
2014-03-06 18:49:16, Error                 CSI    0000009e (F) STATUS_INVALID_PARAMETER #2119208# from PrimitiveInstaller::CCoordinator::FinalizeChanges(...)[gle=0xd000000d]
2014-03-06 18:58:33, Info                  CBS    Scavenge: Package store indicates there is no component to scavenge, skipping.

I searched for "[SR]" but I didn't see anything of great interest

C:\Windows\system32>findstr /c:"[SR]" %windir%\logs\cbs\cbs.log
2014-03-06 18:48:38, Info                  CSI    00000006 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:38, Info                  CSI    00000007 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:39, Info                  CSI    00000009 [SR] Verify complete
2014-03-06 18:48:39, Info                  CSI    0000000a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:39, Info                  CSI    0000000b [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:40, Info                  CSI    0000000d [SR] Verify complete
2014-03-06 18:48:40, Info                  CSI    0000000e [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:40, Info                  CSI    0000000f [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:41, Info                  CSI    00000011 [SR] Verify complete
2014-03-06 18:48:41, Info                  CSI    00000012 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:41, Info                  CSI    00000013 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:41, Info                  CSI    00000015 [SR] Verify complete
2014-03-06 18:48:42, Info                  CSI    00000016 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:42, Info                  CSI    00000017 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:42, Info                  CSI    00000019 [SR] Verify complete
2014-03-06 18:48:42, Info                  CSI    0000001a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:42, Info                  CSI    0000001b [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:44, Info                  CSI    0000001d [SR] Verify complete
2014-03-06 18:48:44, Info                  CSI    0000001e [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:44, Info                  CSI    0000001f [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:45, Info                  CSI    00000021 [SR] Verify complete
2014-03-06 18:48:45, Info                  CSI    00000022 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:45, Info                  CSI    00000023 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:45, Info                  CSI    00000025 [SR] Verify complete
2014-03-06 18:48:46, Info                  CSI    00000026 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:46, Info                  CSI    00000027 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:46, Info                  CSI    00000029 [SR] Verify complete
2014-03-06 18:48:47, Info                  CSI    0000002a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:47, Info                  CSI    0000002b [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:47, Info                  CSI    0000002d [SR] Verify complete
2014-03-06 18:48:48, Info                  CSI    0000002e [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:48, Info                  CSI    0000002f [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:48, Info                  CSI    00000031 [SR] Verify complete
2014-03-06 18:48:48, Info                  CSI    00000032 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:48, Info                  CSI    00000033 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:49, Info                  CSI    00000035 [SR] Verify complete
2014-03-06 18:48:49, Info                  CSI    00000036 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:49, Info                  CSI    00000037 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:50, Info                  CSI    00000039 [SR] Verify complete
2014-03-06 18:48:50, Info                  CSI    0000003a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:50, Info                  CSI    0000003b [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:50, Info                  CSI    0000003d [SR] Verify complete
2014-03-06 18:48:51, Info                  CSI    0000003e [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:51, Info                  CSI    0000003f [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:51, Info                  CSI    00000041 [SR] Verify complete
2014-03-06 18:48:51, Info                  CSI    00000042 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:51, Info                  CSI    00000043 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:52, Info                  CSI    00000045 [SR] Verify complete
2014-03-06 18:48:52, Info                  CSI    00000046 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:52, Info                  CSI    00000047 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:52, Info                  CSI    00000049 [SR] Verify complete
2014-03-06 18:48:53, Info                  CSI    0000004a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:53, Info                  CSI    0000004b [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:53, Info                  CSI    0000004d [SR] Verify complete
2014-03-06 18:48:54, Info                  CSI    0000004e [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:54, Info                  CSI    0000004f [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:54, Info                  CSI    00000051 [SR] Verify complete
2014-03-06 18:48:54, Info                  CSI    00000052 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:54, Info                  CSI    00000053 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:55, Info                  CSI    00000055 [SR] Verify complete
2014-03-06 18:48:55, Info                  CSI    00000056 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:55, Info                  CSI    00000057 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:55, Info                  CSI    00000059 [SR] Verify complete
2014-03-06 18:48:56, Info                  CSI    0000005a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:56, Info                  CSI    0000005b [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:56, Info                  CSI    0000005d [SR] Verify complete
2014-03-06 18:48:56, Info                  CSI    0000005e [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:56, Info                  CSI    0000005f [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:57, Info                  CSI    00000061 [SR] Verify complete
2014-03-06 18:48:57, Info                  CSI    00000062 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:57, Info                  CSI    00000063 [SR] Beginning Verify and Repair transaction
2014-03-06 18:48:58, Info                  CSI    00000065 [SR] Verify complete
2014-03-06 18:48:58, Info                  CSI    00000066 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:48:58, Info                  CSI    00000067 [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:00, Info                  CSI    00000069 [SR] Verify complete
2014-03-06 18:49:00, Info                  CSI    0000006a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:00, Info                  CSI    0000006b [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:00, Info                  CSI    0000006d [SR] Verify complete
2014-03-06 18:49:01, Info                  CSI    0000006e [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:01, Info                  CSI    0000006f [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:01, Info                  CSI    00000071 [SR] Verify complete
2014-03-06 18:49:02, Info                  CSI    00000072 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:02, Info                  CSI    00000073 [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:02, Info                  CSI    00000075 [SR] Verify complete
2014-03-06 18:49:02, Info                  CSI    00000076 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:02, Info                  CSI    00000077 [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:03, Info                  CSI    00000079 [SR] Verify complete
2014-03-06 18:49:03, Info                  CSI    0000007a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:03, Info                  CSI    0000007b [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:04, Info                  CSI    0000007d [SR] Verify complete
2014-03-06 18:49:04, Info                  CSI    0000007e [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:04, Info                  CSI    0000007f [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:05, Info                  CSI    00000081 [SR] Verify complete
2014-03-06 18:49:05, Info                  CSI    00000082 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:05, Info                  CSI    00000083 [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:06, Info                  CSI    00000085 [SR] Verify complete
2014-03-06 18:49:06, Info                  CSI    00000086 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:06, Info                  CSI    00000087 [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:06, Info                  CSI    00000089 [SR] Verify complete
2014-03-06 18:49:07, Info                  CSI    0000008a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:07, Info                  CSI    0000008b [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:07, Info                  CSI    0000008d [SR] Verify complete
2014-03-06 18:49:08, Info                  CSI    0000008e [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:08, Info                  CSI    0000008f [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:08, Info                  CSI    00000091 [SR] Verify complete
2014-03-06 18:49:08, Info                  CSI    00000092 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:08, Info                  CSI    00000093 [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:09, Info                  CSI    00000095 [SR] Verify complete
2014-03-06 18:49:09, Info                  CSI    00000096 [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:09, Info                  CSI    00000097 [SR] Beginning Verify and Repair transaction
2014-03-06 18:49:10, Info                  CSI    00000099 [SR] Verify complete
2014-03-06 18:49:11, Info                  CSI    0000009a [SR] Verifying 100 (0x0000000000000064) components
2014-03-06 18:49:11, Info                  CSI    0000009b [SR] Beginning Verify and Repair transaction

C:\Windows\system32>

I've run into sfc issues in the past, and in one instance, booting the OS install DVD, and running sfc /scannow /offbootdir=c:\ /offwindir=c:\windows did fix the issue.  But I have to ask

Is there no way to do that while in Windows?  Can't I mount some WIM and do it that way instead of booting the DVD?

Is that the right course of action, or is/are there some other options I should explore?

Thanks for your time & guidance.

Hello all

I would like to use PSR over the network. What i mean is i want to be able to run it myself from my PC so that it records the steps on another users machine. Is the possible or is this only a local executable. I have tried starting it by using psexec to open another PC's cmd and then tried starting psr but that didnt work. 

Thank you

So starting on Tuesday January 7th within our school district we are starting to see mice & keyboards (USB) intermittently stop working. Our users are logging off and logging back on and they will work for some time and then stop again. Some back ground information on our systems as well as things we have tried so far:

-All machines were imaged over summer with win7x64

-We keep up to date with windows updates through our wsus server (however we do not release hardware related updates, only critical & security windows updates)

-Everything was working up & until Tuesday, we have made NO group policy changes since then, last time windows updates went out to our network was Dec. 14th and they were working fine before the winter break

-It is happening on several different machines throughout our district, Dell optiplex 760, 9010, 790, as well as laptops with USB mice plugged in

Things we have tried:

-updating bios to most recent A18

-adding specific GUID for mouse, keyboard, & usb related devices for non administrative users to group policy

-un-checking setting for computer to turn off usb ports to converse power

UPDATE: After receiving some great advice from a lot of you guys I went ahead and started looking into the windows update artcle http://support.microsoft.com/kb/2862330, I tried removing KB2862330 on one machine as well as re-installing it on another, still with no success. I also discovered that on October 8th, when this security update went out so did 8 others. In short, 5 were for direct USB core stack & 4 were for Kernel USB. We took one of our labs that has about 20+ machines and on the first 9 we removed 1 update from each of that pack, then on another we removed all 9 updates, and then on another we re-installed all 9 updates. We are still currently waiting on feedback from the users to see if any of those worked before we start trying else where. Has anyone else who commented on this thread found any solutions?

Been scanning through various documents and posts on licensing with VDI. I understand that if a user is accessing a Windows virtual desktop on a server from a non-Windows device then the user must have VDA. If the user is accessing the VDI from a corporate Windows PC then the PC must have Software Assurance. What I do not know is does the VM requires its own license and does that instance also require software assurance? This would result in 2 Windows Licenses and 2 SA subscriptions per user. 

Thanks for clearing up the confusion.