Cannot start remote registry windows 8.1 x64 enterprise
I am trying to install EMC 2010 sp3 on Windows 8.1 Enterprise x64 but the install fails; cannot start remote registry due to credentials. I have tried the credentials that RPC is using, Network Services, but it doesn't work. Have tried other credentials
with same error.
Hi,
Please check if you have installed .net framework 3.5.
The reference is below:
http://social.technet.microsoft.com/Forums/exchange/en-US/aeeedf06-9d9f-4186-9ba9-28c2a2fbaa88/exchange-2010-sp3-installing-on-windows-81server-2012r2?forum=exchange2010
Meanwhile, about this issue, better to post to the forum for Exchange:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchange2010
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Karen Hu
TechNet Community Support
Similar Messages
-
U530 Touch - Audio DRIVER ERROR - This device cannot start (Code 10) - Windows 7
U530 - High definition audio device - ERROR - This device cannot start (Code 10) Windows 7, please see the picture
Picture link (hosted on photobucket.com)
I got all drivers up to date including the BIOS, everything is working fine (the sound works, microphone works...) but this error is kind of annoying to my eyes so if anyone know how to fix it please help.
I tried to uninstall this and let windows update install it again => not worked, same problem.
I tried to re-install the Realtek driver (uninstall - restart machine - install - restart machine) => same problem
And another probelm which has not been solved yet is the Bluetooth icon keep blinking on battery mode (windows 7), you can see more in this threadWhat kind of reinmstall did you perform? If you used the recovery media, then this will be pretty simple. Boot to the recovewry media again and this time select the Reinstall drivers and applications option. Find the audio driver on the list of available drivers, put a tick in the box to its left and then click on the install button in the lower right hand corner of the window. The driver will be installed. Your list will be different than the following one, but this is only an example.
-
"Device Cannot Start - Code 10" - Windows Vista Error, w/ 2nd Gen. Nano
I'm having trouble with my Nano and Windows Vista. The computer is recognizing the iPod just fine and seeing all of my songs, but nothing will play and the diamond bar does not move. I can't hear previews online either.
Under device manager, a yellow "!" shows up for the iPod, and it says "Device Cannot Start - Code 10" when I check. All of my drivers and updates are current as of today. So is iTunes. Any thoughts?
It worked before, but now it's not.This is a reasonably common error on a PC when there is a problem with either a USB device, your USB cables or hardware, or the system drivers.
In a case where, as you say, the device works properly with other computers, the problem is more likely to be with the hardware or drivers on the computer you're trying to connect to.
See this site for some hints:
http://www.pchell.com/hardware/usbcode10.shtml
I found it via a web search; I don't have any connection to that site.
The good news is that your iPhone is probably fine. -
Problem starting LR on Windows 7 PC (x64)
Hello:
I was wondering if someone is having the same problem with Lightroom 2.5 (x64): After installing LR on a Windows 7 PC (x64), the desktop
shortcut is not working. I have tried deleting the shortcut and creating a new one, tried to start LR directly from C:\Program Files\...\lightroom.exe, even re-installed the program, but nothing seems to work.
The only way I can start Lightroom is by running it as Administrator, which is strange because the "Run as Administrator" box in Properties is unchecked, and all other programs (including Photoshop CS4) are starting from shortcuts without any problems.
Any advice would be greatly appreciated.
LucLucN had this to say:
Hello:
Thank you for your feedback. Actually, it was a clean install.
In the meantime I have been able to figure out what the problem was: the Lightroom Catalog was in a directory (on my data HD) other than the default one ("My Pictures" in C:\Users\...).
My catalog is on an entirely different drive than the "default" one.
This way, even if I lose my C: drive, I don't lose the catalog, or the
pictures (I have backups, but I still gain by not having to restore all
that, as well as the OS, in the event C: dies) -
See original question. Firefox apparently doesn't close when using the x in upper right corner as when I try to start it again I get a message that FF is already running and I must close it first. I thought the x would do that. Is something set wrong or corrupted?
ThanksSee "Hang at exit":
* http://kb.mozillazine.org/Firefox_hangs
* [[Firefox hangs]] -
I am new to Gen2 Hyper-V and so far I simply can't use it, because I am unable to install any (supported) guest OS from an ISO ...
So far I tried that on:
1. my HP Z230/i4770 workstation (Secure Boot disabled) host running Windows 8.1 Pro x64 (with Hyper-V feature enabled), can't boot any VM with supported OS ISO.
2. my home desktop/i3770K (secure Boot enabled) host running Windows 8.1 Pro x64, same result, error during VM boot from ISO, quoted below.
Synthetic SCSI controller (instance blah blah) Failed to Power on with Error 'The version does not support this version of file format'
Gen1 guests of course work perfectly fine with those ISOs, because emulated DVD IDE picks up the official Enterprise Evaluation ISO of either Windows Server 2012 R2 or Windows 8.1 x64 Enterprise, perfectly fine and all works OK in Legacy boot mode.
When I create a new guest and select Gen2, then no matter if I check or uncheck the Secure Boot in virtual Boot Order options for the guest (while setting the SCSI DVD at top of course), it simply doesn't work, always same error. I tried first connecting
to VM to see if it prompts for key press, but it doesn't, the error is instant on Power on when (supported) ISO image is selected to be booted.
I verified that both of official Enterprise Evaluation ISO's of either WS2012r2 and W8.1x64 are bootable in both the UEFI mode (Secure Boot enabled) and Legacy BIOS mode using a physical computer.
What am I missing here???FYI, above is wrong! it's not about linking ISO to virtual DVD or selecting "Install OS later", it's all about the location of the ISO file and share permissions on parent folder!
I was actually suspecting several issues, but haven't had time to test it, was thinking about issues like assigning (or not) some of initial settings during Gen2 VM creation, e.g.:
-Network connection through virtual switch or Not Connected (make no different if assigned or not)
-Memory above 4096MB (makes no difference if < or > 4096MB)
-ISO file location (makes huge difference!)
The ISO file CANNOT be placed on network share OR in shared folder on same local drive as the VHDX file (works fine if parent folder is not shared).
I can now replicate the issue easily every time and it always fails with file format unsupported message whenever I have the ISO file located either on remote network share, or (fails the same way too) when I have the ISO file placed locally (on host drive)
when simply a parent folder is shared... must be some permissions issue... and a pretty dumb one considering that in production environments nearly everything is placed on remote file servers ...
... so the moral of the story is, if you want to install Gen2 VM in win8/2012 hyper-V then you must copy the ISO file to Hyper-V host drive AND make sure the parent folder is not shared. works every time now! :) -
IdeaPad U410, Windows 8.1 x64, UEFI, Intel Smart Response problem
Hi,
My machine was running a Windows 8.1 x64 Enterprise on a GPT partitioned HDD UEFI enabled with bios version 65CN21WW.
Intel Smart response and rapid start was running fine with the 32GB Samsung SSD.
After upgraded the bios to version 65CN99WW many weird thing happened:
- the system couldn't start, it tried to repair the system on booting,
- The bios shows the machine as U310 model,
- Even after a fresh install of the windows the machine couldn't start after finishing the install.
I finally got the system working by reseting the RAID and installing the system without acceleration association in UEFI mode. But after enabling the acceleration in the Rapid Storage UI the system starts to failing again and tries to repair the system again and again.
By disabling the UEFI, (setting it to legacy support) the system could start again.
Why cannot the UEFI be enabled? Or what is the correct setup in the BIOS?
Any help appreciated!
Regards,
R.Why did you upgrade the BIOS?
I'm still keeping the old CN21 and it works perfectly with 8 Gb RAM and the new 512Gb M6 from Plextor, I barely finish typing the logon pass and windows 8.1 screen shows up.
Admin Edit: edited potentially offensive language -
Windows Server 2008 x64 on Bootcamp: Ethernet drivers missing/not working
Hello folks,
at the moment I try to get Windows Server 2008 x64 running on a new Mac Pro (Early 2009).
Installation of Windows Server 2008 x64 (Enterprise) worked out of the box. However, the ethernet drivers do not work. Ethernet cards are not detected and working due to missing drivers.
I have tried several different Intel driver packages. All of them report "No intel card found.". However, the vendor ID of the ethernet card clearly points to Intel.
I have not been able to find a driver yet, does anyone have an idea?
E.g. does someone know the exact chip name? The driver "name"? Anything else?
Thank you in advance,
StefanErik - Thanks for the info!
I use 64-bit applications ... some notes on why:
enterprise supports up to 32GB of memory so the argument to use x64 for memory support is nullified.
... that's not correct. x64 windows versions allow 64-bit addressing, so 64-bit applications created for x64 windows can take advantage of large amounts of cheap RAM as 32-bit applications cannot. 32-bit applications (they are all 32-bit applications in a 32-bit Windows version, even in Server 2008) are restricted to a limited process space of at most 2 GB.
It's true there is a LARGEADDRESSAWARE kludge to enable limited use of up to 3 GB by a user process (and there is an equivalent to this in Server 2008), but this has gone nowhere because it is far more straightforward and more productive for an applications developer to simply go 64-bit rather than invest any engineering resources into a one-of-a-kind kludge for an era that is already past.
Yes, it is true that if you are stuck running 32-bit applications you have less incentive to use x64 windows. But going true 64-bit is a huge advantage in reliability and performance. Given the very low cost of RAM in modern times it makes sense to do so, even in notebook settings that are often limited to only 4 GB of RAM. 64-bit applications in Windows tend to have decisive performance and reliability advantages so whenever one competitor in a given segment makes the jump to 64-bit pretty much all of them must do so. -
I have tried to install Oracle 9i (9.2.0.2) in Windows Server 2003 x64 Enterprise Edition with Intel Xeon (EM64T) processors.
When I run setup.exe I get an error: "The image file C:\Documents and settings\administrator.SERVERNAME\my documents\92021 win64_disk1\setup.exe is valid, but is for a machine type other than the current machine".
I have to install Oracle 9i in that server but I can't run the installation. Is there a way to solve this problem, is there a patch that can solve this? Anyone know something about this problem?
Thanks a lot!!!
I'm desperated!!Hi,
reply to my own question:
In the docs provided with the downloads for Oracle Database Server 9i x64, I found that this version requires either
- Windows Server 2003 Datacenter Edition for 64-Bit Itanium 2 Systems
or
- Windows Server 2003 Enterprise Edition for 64-Bit Itanium 2 Systems
So I guess, the only X64 platform being supported under Windows Server 2003 (both Datacenter / Enterprise Editions) is Itanium CPUs ...
... though this is not (!!!) clearly stated in the download link (other/newer versions are listed more precisely - I guess it's a matter of an old link: no Intel Xeon / AMD Opterons were available (???) when Oracle 9i database server was published).
So I'll give it a try with 10g database server ;-)))
Regards,
Thomas Heß -
I have trouble with Windows Server 2003 R2 Standard. I installed the KB2893294(MS13-098) patch, and I changed the registry that is suggested actions of Security Advisory(2915720) http://technet.microsoft.com/en-us/security/advisory/2915720
Suggested Actions:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Wintrust\Config]
"EnableCertPaddingCheck"="1"
After rebooting the event viewer(system) says:
Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1014
User: N/A
Description:
Cannot load illegal module: C:\Windows\system32\rdpwsx.DLL
After I cannot use Remote Desktop Connection from other client.
So I check the all security patches and other hotfixies. I checked the KB2653956 and KB958476.
But TermService do not recover the error.
And then, I delete the "EnableCertPaddingCheck" registry and reboot systems.
TermService have no error. I can use Remote Desktop Connection from other client.
After KB2893294 installed, Remote Desktop Connection cannot use from other client that "EnableCertPaddingCheck" registry set to "1".
Other Windows Server 2008 systems do not effect the KB2893294 patch. But All Windows Server 2003 systems cannot use the Remote Desktop Connections after the KB2893294 patch.Update on this issue:
The debug team has accepted the issue and has identified it as a regression. Right now they're targeting *June* as the release date for a fix. I'm attempting to educate them that customers don't just install patches the day (or even month) they're
released and that the fix needs to be moved up in priority to give a minimum of 60 days to install the patch before the time-bomb explodes.
In the meantime, a workaround has been provided that will turn off the new functionality. Note that I have not yet had a chance to test this. It entails creating a new DWORD registry entry--UseLegacyPE--and setting it to 1.
HKLM\Software\Microsoft\Windows NT\CurrentVersion\ImageHlp\UseLegacyPE
I will update this thread when I have further information. -
Cannot use Remote Desktop host on Windows 8.1 Pro, termsrv corrupted?
Hello,
Few days ago I upgraded my home desktop machine from Windows 8.1 to Windows 8.1 Professional so I can use the Remote Desktop feature.
I enabled everything needed, checked "Allow computers to connect to this computer" from the Remote Settings, forwarded the port 3389 in my rounter and allowed it in my firewall etc...
But I still can't connect to this computer from outside my home network or inside it. The error I get trying to connect is this:
(For some reason i still can't post images in this forum...) So I posted a link below to my original thread with the images
I'm trying to connect using a laptop running Windows 7 Home Premium.
After searching around I found out that the service responsible for the RDP is called "TermService", I found it on my services but was unable to start it:
(For some reason i still can't post images in this forum...) So I posted a link below to my original thread with the images
Also, notice the description of the service. So I tried to run a System File Checker on the service's DLL (sfc /scanfile=c:\windows\system32\termsrv.dll) and got this log:
2014-10-05 14:20:41, Info CBS TI: --- Initializing Trusted Installer ---
2014-10-05 14:20:41, Info CBS TI: Last boot time: 2014-10-05 13:56:05.492
2014-10-05 14:20:41, Info CBS Starting TrustedInstaller initialization.
2014-10-05 14:20:41, Info CBS Ending TrustedInstaller initialization.
2014-10-05 14:20:41, Info CBS Starting the TrustedInstaller main loop.
2014-10-05 14:20:41, Info CBS TrustedInstaller service starts successfully.
2014-10-05 14:20:41, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2014-10-05 14:20:41, Info CBS Startup processing thread terminated normally
2014-10-05 14:20:41, Info CBS Starting TiWorker initialization.
2014-10-05 14:20:41, Info CBS Ending TiWorker initialization.
2014-10-05 14:20:41, Info CBS Starting the TiWorker main loop.
2014-10-05 14:20:41, Info CBS TiWorker starts successfully.
2014-10-05 14:20:41, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:41, Info CBS Universal Time is: 2014-10-05 11:20:41.783
2014-10-05 14:20:41, Info CBS Loaded Servicing Stack v6.3.9600.17246 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17246_none_fa4ae8e99b1f603c\cbscore.dll
2014-10-05 14:20:41, Info CSI 00000001@2014/10/5:11:20:41.786 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffee15c60e5 @0x7ffeeace2e53 @0x7ffeeace24ac @0x7ff69a94d2df @0x7ff69a94dc97
@0x7fff02912225)
2014-10-05 14:20:41, Info CBS SQM: Initializing online with Windows opt-in: True
2014-10-05 14:20:41, Info CBS SQM: Cleaning up report files older than 10 days.
2014-10-05 14:20:41, Info CBS SQM: Requesting upload of all unsent reports.
2014-10-05 14:20:41, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2
2014-10-05 14:20:41, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2014-10-05 14:20:41, Info CBS NonStart: Set pending store consistency check.
2014-10-05 14:20:41, Info CSI 00000002@2014/10/5:11:20:41.801 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffee15c60e5 @0x7ffef3637fc0 @0x7ffef36380f2 @0x7ff69a94ca25 @0x7ff69a94dcae
@0x7fff02912225)
2014-10-05 14:20:41, Info CSI 00000003 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x559943db20
2014-10-05 14:20:41, Info CSI 00000004 Creating NT transaction (seq 1), objectname [6]"(null)"
2014-10-05 14:20:41, Info CSI 00000005 Created NT transaction (seq 1) result 0x00000000, handle @0x26c
2014-10-05 14:20:41, Info CSI 00000006 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
2014-10-05 14:20:41, Info CSI 00000007@2014/10/5:11:20:41.999 Beginning NT transaction commit...
2014-10-05 14:20:41, Info CSI 00000008@2014/10/5:11:20:41.999 CSI perf trace:
CSIPERF:TXCOMMIT;143
2014-10-05 14:20:42, Info CSI 00000009 CSI Store 367642371808 (0x00000055993166e0) initialized
2014-10-05 14:20:42, Info CSI 0000000a [SR] Verifying 1 components
2014-10-05 14:20:42, Info CSI 0000000b [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:42, Info CSI 0000000c [SR] Verify complete
2014-10-05 14:20:52, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:55, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:55, Info CSI 0000000d [SR] Verifying 1 components
2014-10-05 14:20:55, Info CSI 0000000e [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:55, Info CSI 0000000f Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000010 [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 00000011 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000012 [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 00000013 [SR] This component was referenced by [l:154{77}]"Package_3_for_KB2959626~31bf3856ad364e35~amd64~~6.3.2.0.2959626-3_neutral_GDR"
2014-10-05 14:20:55, Info CSI 00000014 Hashes for file member \??\C:\Windows\System32\termsrv.dll do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000015 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000016 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll"; source file
in store is also corrupted
2014-10-05 14:20:55, Info CSI 00000017 [SR] Verify complete
2014-10-05 14:20:55, Info CSI 00000018 [SR] Repairing 1 components
2014-10-05 14:20:55, Info CSI 00000019 [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:55, Info CSI 0000001a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 0000001b [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 0000001c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 0000001d [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 0000001e [SR] This component was referenced by [l:154{77}]"Package_3_for_KB2959626~31bf3856ad364e35~amd64~~6.3.2.0.2959626-3_neutral_GDR"
2014-10-05 14:20:55, Info CSI 0000001f Hashes for file member \??\C:\Windows\System32\termsrv.dll do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000020 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000021 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll"; source file
in store is also corrupted
2014-10-05 14:20:55, Info CSI 00000022 [SR] Repair complete
Since it's the first time I use this tool I'm not familiar with this log file, but what I managed to figure out from it is that termsrv.dll is corrupted and windows cannot repair it for some reason.
My question is:
How can I repair this file? Is this even the problem preventing me from connecting to this computer via Remote Desktop?
Here's a link to my original question which contatining the images.
http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/cannot-use-remote-desktop-host-on-windows-81-pro/e4776239-4d9e-4934-ae2d-b87cc09f7ademanaged to figure out from it is that termsrv.dll is corrupted and windows cannot repair it for some reason.
So, the next step supposedly is
using DISM.
Coincidentally I reached that page last night from
this one, which I thought gave me a better awareness of how much manual repair might be possible. E.g. maybe the WinSxS isn't quite as fragile as we are being led to believe? (It's making me feel sort of like how I used to feel about the
registry when seeing all the caveats about using RegEdit before I got used to that tool.)
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779(v=WS.10).aspx
Something else that I became aware of yesterday serendipitously is SxStrace.exe. I have never seen it used but it sounds useful. E.g. perhaps easier to interpret for supplemental clues than the ProcMon trace that I usually advocate.
Or perhaps use both and see in ProcMon when the SxStrace is writing. E.g. filter with Operation Is WriteFile.
However, what I would do first is find out what the state of your system is regarding that module. E.g. try this Powershell pipeline to list what you have.
PS C:\windows> dir -R -Fil "termsrv.dll" | sort-object FullName | ft Length, FullName -AutoSize
Note that I am giving you the whole command line, including prompt to show where the command should be started from.
C.f. another thread where doing the same diagnostic procedure seems to be finding more a problem with the Windows Update software than with the user's WinSxS cache.
http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_store/windows-81-store-error-0x80070002-comprehensive/2b0ed3e1-1835-4517-97dd-0a7abb6ef74c?page=3#LastReply
HTH
Robert Aldwinckle -
CD/DVDW SN-S082D issue - Windows cannot start this hardware device Code 19
I've had my laptop for a little over a year now and it's had it's fair share of problems, most of which are fixable or there is a workaround.
Earlier today I inserted a disc into the drive and tried opening it up, went into "My Computer" and found the disc drive was not listed.
This has happened once or twice before and a simple restart fixes the problem.
I've restarted twice and this time the problem wasn't fixed, after going into "Device Manager" I found there was a problem with the device and it gave me the following error
"Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)
Click 'Check for solutions' to send data about this device to Microsoft and to see if there is a solution available."
As usual 'Check for soulutions' is useless and returned no results.
Thanks in advance for any replies.
Some info that may help
OS: Windows Vista Home Premuim
Laptop Model / Number: Medion MD 98300
DVD Drive: TSSTCorp CD/DVD W SN-S082D ATA Device
ThanksFirst of all I wonder why you post this here in the Toshiba forum if you dont have a Toshiba notebook
This is a little bit strange for me... anyway I will try to help you.
It seems that the registry keys are corrupt and therefore your CD/DVD drive cannot work properly.
Try simply the solution proposal mentioned here in the Microsoft doc:
http://support.microsoft.com/kb/270008/en-us
Good luck -
Windows 7 Pro x64 now BSOD just as it is starting and Startup Repair has failed
As the title says, a few days ago my Windows 7 Pro x64 started to BSOD just as Windows is starting but the error screen disappears immediately.
Startup Repair fails and has Problem Signature 04: 21199350
I have used the Windows 7 Pro installation DVD and opened its Command Prompt option and then run the chkdsk and sfc programs but no errors were reported. Also, I ran bootrec with /fixmbr then with /fixboot and finally with /rebuildbcd but it made no difference.
After a failure, the next time I turn on the PC I am offered to repair Windows or to start windows normally. Using the repair from here didn't work as also happened when I chose the repair option from the Windows 7 Pro installation DVD.
Holding down the f8 key when Windows is starting doesn't make any difference.
BTW, the crash happens as the 4 small parts of windows are approaching each other on the Windows start screen.
I can access my hard disk by attaching it to my laptop. If the error 21199350 reported by Startup Repair failure is not the BSOD error, will this be recorded in a file each time it happens? If so, which file?
Any help will be greatly appreciated as I dread having to reinstall Windows 7 Pro from scratch again and all the many programs I spent ages installing.
Thanks
PaulSorry for the delay in replying.
This evening I managed to modify the PC registry from the Startup Repair command window so it wouldn't reboot on BSOD.
Used regedit.exe to modify the following in the PC's registry (I followed the 17 July 2011 Terra-byte "Modify the Windows Registry from Startup Repair" article):
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CrashControl] and set AutoReboot to 0x00000000.
and also for ControlSet002.
The BSOD error is: 0x0000007B which seems to be a device driver problem.
Would my problem be caused by my installing 2x 2GB DIMMs that I bought on eBay into my Abit AB9 Pro motherboard's two free slots (the other two slots each have 1GB DIMMs) but on power on nothing happened?
Removing the two new DIMMs the PC powered on but then resulted in BSOD.
Thanks
Paul
Error 0x000000tB is a very often reported error. It means INACCESSIBLE BOOT DEVICE. Either something in your BIOS changed the type of storage device (AHCI -> IDE) or your HDD is experiencing a possible failure.
See info @ 0x0000007B (INACCESSIBLE BOOT DEVICE): Fix for Windows XP, Vista, 7, 8, 8.1
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” -
So here is the error in Outook 2013
"Cannot start Microsoft Outlook. Cannot open the Outlook window.
The information store could not be opened."
Very Very frustrating having spent three hours today reading forums, installing, reinstalling etc.
HELP?
1) I have completely un-installed and reinstalled Outlook 2013 (And also all of Office 2013)
2) Have blown away all profiles and created new ones.
3) Have blown away all Outook data files and starting from scratch
4) Have run /resetnavpane............in an attempt to rebuild the navigation pane
5) Have gone into Registry and deleted all remnants of previous Outlook installs, HKey_Local, System Current
config......Office etc.
6) I have spent hours reading online fixes/technet forums etc..............to no avail.
Please give more suggestions.
Thanks
Phil H Charlotte, NCHi,
Basically you have tried a lot but the issue still exists, now one more suggestion I can provide is to make sure Outlook is not configured to run in Compatibility Mode:
Take Windows 7 for example, in Start -> Type "Outlook" in the search box -> Right click on the "Outlook 2013" shortcut -> Click Properties -> Under Compatibility tab -> Make sure "Run this program in compatibility
mode for" is clear.
This method has resolved the issue for some users in this thread below:
http://answers.microsoft.com/en-us/office/forum/office_2007-office_install/cannot-start-microsoft-office-outlook-error-cannot/e75265b4-044f-4d92-a078-1acbf9ae34d6
I hope the information is helpful.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs. -
cannot open pictures in Window 8.1...getting message 'the remote procedure call failed". What is the solution?
I recently bought a new HP computuer and uploaded Window 8.1. I then transfered photo files from old computer to new computer using a portable storage drive.
When trying to view the photos, a message pops up showing a file path...and the message 'the remote procedure call failed'. Photos are in jpeg format.
Please let me know what I can do to view photos?What program you use to view these photos? Choose another app to view these photos
for a test.
This issue only occurred when you view photo? What is the result if we connect the
portable storage drive to other computer (if possible)?
Run sfc/scannow to check and fix if there are some missing or corrupted system files.
Check the event viewer to see the detailed information of this issue.
Regards
Yolanda
TechNet Community Support
Maybe you are looking for
-
Zone Cluster: Creating a logical host resource fails
Hi All, I am trybing to create a logical host resource with two logical addresses to be part of the resource, however, the command is failing. Here is what I run to create the resource: clrslh create -Z pgsql-production -g pgsql-rg -h pgprddb-prod,pg
-
Photoshop Elements 9 Locking Up
Immediately upon loading Photoshop Elements 9 the program locks up. Restarting does not help. Running 64bit quad core processor. 8 Ram. Any Ideas. This has been a constant problem since loading on new compurter last year.
-
Port Forwarding Comcast Modem/Router for enabling ...
The process of port forwarding seems long and complicated. Is the Freetalk Connect Me phone adapter, which is no longer offered by Skype, worth it? I'd like to begin using my Skype service and use Comcast only for internet. The modem/router I use now
-
What is Forecast methodology? How we should decide what forecast methodology is required for particular scenario?Which forecast model is suitable ? Whether we should go for univariate or MLR ? Thanks in advance, Prabhat
-
My ipod is stuck at step 9 in this guide. Itunes told me to keep my ipod connected to itunes, and my Ipod shows the Apple logo as it should (though I can´t see any progress bar). Do anybody know how long step 9 takes. I have turned off my firewall.