Hi,
in Server manager i disabled the IE ESC.
But, when i open IE i see that ESC is still enabled.
How can i disable IE ESC on 2016?
Thanks.
↧
Disable IE ESC 2016
↧
8dot3 Performance Gains
We use a file server here that runs Server 2008 R2. It hosts close to 500,000 files and we still have 8dot3 short names turned on the drive. I've read about the performance gains by turning that off, but I don't know how much of an improvement we'd
see or where. Is it faster when creating a single file? Would we only see gains when doing bulk file/folder manipulations? Since it's possible something somewhere might not work if I turn it off, I'm wondering how much gain I'd likely see. Can anyone provide
some insight? Thanks.
↧
↧
Cannot install KB4338815 on Windows Server 2012 64: Windows Update Error 800F0922
Hello,
I'm unable to install the latest cumulative update for Windows 2012 Server.
After reboot Windows rolls it back.
I've tried four times already. Wiping c:\Windows\SoftwareDistribution\Download doesn't help.
Here's the last CBS.log file https://1drv.ms/u/s!AvORQXCuVlB3iHsXLG7Z8fLXAdrF
I need to understand what's wrong with my PC. I've been successfully using this server installation for three years and it's the first time an update fails.
Is this because this update is borked ( https://www.computerworld.com/article/3290948/microsoft-windows/microsoft-dives-down-a-bizarre-non-cumulative-rabbit-hole-with-july-patches.html )?
↧
Cannot get rid of 169.xx.xx.xx IP address on new Server
I did a fresh install of Windows Server 2016 on VM Esxi Virtual machine. The server acquired some weird IP address starting with 169.xx , I ignored and gave it a static IP in the local network(all other systems working fine with these range of IPs).
Now this new server does not accept this IP (shows it as duplicate) and that 169.xx IP is taken as preferred. I tried all possible way to get rid of that default IP and assign it a static LAN IP.
Please suggest.
↧
DNS Resolve with RRAS
I have a VPS running WS 2016 (not AD). I host some .net applications on the machine and machine has own DNS Server with two dedicated public IP. Everything was fine without RRAS configuration, but I needed a VPN service and added one virtual NIC to configure
RRAS. While RRAS active, I cannot reach my VPS via Remote Desktop, also my host sites are unavailable due name resolution error. My RRAS configuration as follows:
Appreciate for help.
↧
↧
Single Label Domain, DNS, and DHCP
A client of ours recently upgraded servers from 2012 R2 to 2016 but is still running on a single label domain. We were going to migrate to a full FQDN but the client decided to not do that just yet to save on time (I believe). I also upgraded the forest and domain levels from 2003 to 2012 R2. With the combination of the upgraded OS and greatly upgraded forest and domain levels, a few issues began to bubble to the surface.
First, we noticed issues with AD replication and saw that the network was still using FRS. We migrated this to DFSR and resolved those issues. Currently what we're seeing now is issues with DHCP. DNS, obviously, is still configured with the single label (i.e. COMPANY). DNS appears to be working as it did before the migration, at least in terms of resolving queries. DHCP is currently set up with options 03 (router) and 06 (DNS servers). Options 04 (time server) and 46 (NetBIOS over TCP/IP node type) were removed since they appeared to be superfluous.
As DHCP leases expire, however, the client is stating that they cannot renew leases and must reboot the PC. Once they do this, the PCs receive a new lease and continue working normally. After reading many, many articles including Active Directory DNS Single Label Names (thank you, Ace), the issues appears to me to be clearly that the domain is still still single label and cannot properly function interact with DHCP and DNS. The client, however, is arguing that this should have nothing to do with the problems they're seeing.
I'm hoping someone can give a more definitive answer since it's pretty clear that the technology, though it might have worked even through 2012 R2, simply is a throwback to NT4. As a last fact, WINS was being used on the network prior to the migration to 2016 but was not migrated because it was believed to be too old and irrelevant. If we're told that this must be re-implemented it will be.
Thank you↧
Administrator
MKCC
↧
Windows Server 2008 R2 Update fails due to system-protected font
Hello,
My windows Server 2008 R2 has been failing to install the
2018-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4338818)
every day for many days (it was already failing the preview of it, which I then declined on WSUS).
The only apparent problem I see in the WindowsUpdate.log is this (in bold below):
...
2018-07-17 07:41:08:522 856 169c Report *********** Report: Initializing static reporting data ***********
2018-07-17 07:41:08:522 856 169c Report * OS Version = 6.1.7601.1.0.196880
2018-07-17 07:41:08:522 856 169c Report * OS Product Type = 0x00000007
2018-07-17 07:41:08:678 856 169c Report * Computer Brand = Dell Inc.
2018-07-17 07:41:08:678 856 169c Report * Computer Model = PowerEdge R210 II
2018-07-17 07:41:08:678 856 169c Report * Bios Revision = 2.8.0
2018-07-17 07:41:08:678 856 169c Report * Bios Name = InsydeH2O Version 03.70.452.8.0
2018-07-17 07:41:08:678 856 169c Report * Bios Release Date = 2014-06-24T00:00:00
2018-07-17 07:41:08:678 856 169c Report * Locale ID = 1033
2018-07-17 07:41:08:694 856 3b0 Handler Post-reboot status for package Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24180.1.8: 0x80070020.
2018-07-17 07:41:08:694 856 3b0 Handler WARNING: Got extended error: "POQ Operation HardLinkFile OperationData \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_6.1.7601.24145_none_8e5c4f96a47869ce\tahomabd.ttf, \??\C:\Windows\fonts\tahomabd.ttf"
2018-07-17 07:41:12:640 856 3b0 AU ########### AU: Initializing Automatic Updates ###########
2018-07-17 07:41:12:687 856 3b0 AU # WSUS server: http://whiskey
2018-07-17 07:41:12:687 856 3b0 AU # Detection frequency: 22
2018-07-17 07:41:12:687 856 3b0 AU # Approval type: Scheduled (User preference)
2018-07-17 07:41:12:687 856 3b0 AU # Scheduled install day/time: Every day at 6:00
2018-07-17 07:41:12:687 856 3b0 AU # Auto-install minor updates: Yes (User preference)
2018-07-17 07:41:12:687 856 3b0 AU # Will interact with non-admins (Non-admins are elevated (Policy))
2018-07-17 07:41:12:750 856 3b0 AU Setting AU scheduled install time to 2018-07-18 09:00:00
2018-07-17 07:41:12:750 856 3b0 AU Successfully wrote event for AU health state:0
2018-07-17 07:41:12:750 856 3b0 AU Initializing featured updates
2018-07-17 07:41:12:750 856 3b0 AU Found 0 cached featured updates
2018-07-17 07:41:12:750 856 3b0 AU Successfully wrote event for AU health state:0
2018-07-17 07:41:12:750 856 3b0 AU Obtained Post reboot hr from Agent:80070020
2018-07-17 07:41:12:781 856 3b0 AU WARNING: Post-reboot install failure, error = 0x80070020
2018-07-17 07:41:12:781 856 3b0 AU AU setting pending client directive to 'Forced Reboot'
2018-07-17 07:41:12:796 856 3b0 AU Successfully wrote event for AU health state:0
2018-07-17 07:41:12:796 856 3b0 AU Triggering Offline detection (non-interactive)
2018-07-17 07:41:12:796 856 3b0 AU Successfully wrote event for AU health state:0
2018-07-17 07:41:12:796 856 3b0 AU AU finished delayed initialization
...
2018-07-17 07:44:49:528 856 104c Report REPORT EVENT: {3A6776D8-A21A-42AA-BED5-F975A6DE086E} 2018-07-17 07:41:12:640-0300 1 182 101 {1C930EAB-7B7E-4616-B5B5-D6E4A723BC71} 200 80070020 AutomaticUpdates Failure Content Install Installation
Failure: Windows failed to install the following update with error 0x80070020: 2018-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4338818).
2018-07-17 07:44:49:528 856 104c Report REPORT EVENT: {34F70FF8-C07D-4190-AC13-E7B3CFAFEA9F} 2018-07-17 07:41:12:750-0300 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
That font (tahomabd.ttf) is a system-protected font, so I suppose the update fails as it cannot overwrite it.
I've found a similar issue that required a fix, but for Vista and Windows Server 2008 (not R2):
https://support.microsoft.com/en-us/help/980248/some-font-files-that-are-marked-as-system-protected-cannot-be-updated
Any hints on how I can complete this update?
Thanks!
↧
Windows Server Standard 2016 OEM License as an OS for a VMWare Virtual Machine
Hi everyone,
Can a Windows Server Standard 2016 acquired as an OEM license be used as an OS for a VMWare Virtual Machine?
Any chance you can direct me to the documentations?
Thanks in advance!!
Kind regards,
Ryan
↧
↧
schannel 36881
"The certificate received from the remote server has either expired or is not yet valid. The TLS connection request has failed. The attached data contains the server certificate."
I have servers getting this message, trying to connect to my domain controllers. I don't know if it is causing a problem or not, but would like to get rid of this meesage from the system eventlog of my servers to eliminate it as being a problem. How can I address this error?
To be more specific, one server getting this message trying to connect to my DC is an sql/ERP server. Another server is a citrix xenapp vda server. I think the connections have to do with ldap. Any assistance is appreciated.
capitan
↧
Windows Server 2012 Event ID 4231
Hello,
I am experiencing Event ID 4231 in several of my servers. (all ports being in use). After which I am unable to remote desktop into it. I can only restart it.
However, we are running a count on the ports being in use every 5 minutes and do not see an abnormal increase (below 500).
I have read some sites which mention that it's due to some Microsoft Patches. However, we only install security patches and this is only happening to some of my servers (with DB installed) and not all. I read the below
https://social.technet.microsoft.com/Forums/sharepoint/en-US/8d29f351-6bc4-4ad8-9fcc-02d827e05536/ephemeral-port-exhaustion-event-id-4231?forum=winserver8gen
We have no iSCSI disks being used as well.
Appreciate any help I can get. Thank you
↧
Occasionally got 'Request timed out' when trying to do Ping test on the server. What likely will be the cause?
I want to troubleshoot what causing the connection unstable between workstation and server. When i try do the ping test, the reply sometime 'Request timed out' Any idea what likely the cause of this issue?
I tried change network adapter, change network cable, change network port, reassign different ip address to the server. Still the result remain. I got another server on the same rack and same ip segment(base), but the other server is ok.
Any idea on this guys?
Thanks.
↧
Time Configuration in Active Directory via GPO - Windows 2012 R2 not working.
I followed the link "https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/" to configure NTP via GPO however I did not find Computer
Configuration\Administrative Templates\System\Windows Time Service. Instead I found Computer Configuration\Administrative
Templates\System\Enable Windows NTP Server\Windows Time Service which is not working. Does anyone aware of GPO configuration in Windows 2012 R2 about how to configure NTP server.
Shashi
↧
↧
error code 0x0000232B RCODE_NAME_ERROR Windows 10 Ver 1803
What I have is a Client Windows 10 Pro Ver 1803 all patched with a Windows server 2012 R2 domain controller
when trying to join the domain I get the error (I have changed some of the text for security reasons)
The domain name "XXXXXX" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "XXXXXX":
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.XXXXXX
Common causes of this error include the following:
- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS.
These records are registered with a DNS server automatically when a AD DC is added to a domain.
They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
192.168.XXX.XXX
192.168.XXX.XXX
192.168.XXX.XXX
- One or more of the following zones do not include delegation to its child zone:
XXXXXX
. (the root zone)
Like I said above this is a windows 10 Pro client updated to the 1803 version.
I can ping the DNS server. I can do a nslookup on the DNS server and both work fine. I can ping and nslookup on other servers and they work fine
I can type in the path to a folder on a server in the search box on the task bar and it opens the folder.
I have put the DNS server IP directly into the network properties on the client and it did not help.
I disabled the IPV6 and this did not help.
This is the 3rd client this has happened to me. So far the only thing I have been able to do is RE-Install windows 10 and at the 1703 version join the domain (Which it does with no problems) and then update the system to the 1803 Version.
Does anybody have an Idea what is wrong with the 1803 Version that it will not join a domain.
Thanks
Joel
Just an update. I did a revert back to previous version and set it back to version 1709.
with out doing anything else. I then tried to join the domain and it worked with NO ERROR. There is something wrong with the 1803 version that it will not join my domain. Some setting that Microsoft has changed.
Thanks
Joel
↧
KB4338815 KB4284815 KB4339093 KB4338824 vCenter Server 6.0 U2 Host Network Connection Failure
The week before we installed July 2018 MS patches on the vCenter server (runs on Windows 2012 R2). A couple of days later we encountered frequent disconnects of the hosts in our environment from the vCenter server that cited host network connection failure
(host running vmware esxi 6.0).
Based on vmware support recommendation we uninstalled KB4338815 only to find that KB4284815 was installed automatically during the uninstall of the first one. That did not resolve the issue. Instead it got worse. More frequent disconnects that would last
for about 10 seconds. Then we proceeded to remove all the updates from July. After that we have not seen the disconnect for the past three days. Touch wood!
Please share your experience if you have witnessed the above and what resolutions were taken. I wanted this thread out there so that others in the same boat may find an easy fix by uninstalling the updates and that someone from MS would take notice. What
a nightmare!
↧
Event Log Forwarding (PUSH) not working - collector HTTP URL not available
Given the requirements vary with Collector initiated vs. Push collection of events, note that I'm only using the Push method.
I have a Win10 Collector and two clients, Win10 & Win7. All of the machines are in the same domain.
Since I'm using Push, I did not perform any special configuration on the clients. I did everything via GP.
1. Configured the subscription manager. Server=http://mycollector.fabrikam.com:5985/wsman/SubscriptionManager/WEC,Refresh=60
2. Allowed remote server management though WinRM. ALL IP's
3. Enable WinRM to automatically start - which it does on all machines.
I get this on both Clients:
The forwarder is having a problem communicating with subscription manager at address http://mycollector.fabrikam.com:5985/wsman/SubscriptionManager/WEC. Error code is 2150859027 and Error Message is <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859027" Machine="Win7Ex64.fabrikam.com"><f:Message>The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. </f:Message></f:WSManFault>.
This message appears roughly every 60 seconds in the Win7 log but very seldom in the WIn10 log.
So the clients obviously see the subscription and try to contact the Collector but fail.
I can ping the server by name and the firewall rule for port 5985 is enabled.
Lastly, I set up an additional Collector on a Server 2012 R2 machine and added it to the subscription GP. Both machines reported the same error connecting to it.
Not sure what else to try. Any suggestions are appreciated.
↧
Windows Server 2016 Event 1000, Application Error Faulting application name: mmc.exe
Faulting application name: mmc.exe, version: 10.0.14393.2097, time stamp: 0x5a820e5d
Faulting module name: GPOAdmin.dll, version: 10.0.14393.2068, time stamp: 0x5a7e7062
Exception code: 0xc0000005
Fault offset: 0x00000000000be1d6
Faulting process id: 0x3a8
Faulting application start time: 0x01d428f2d03e703a
Faulting application path: C:\Windows\system32\mmc.exe
Faulting module path: C:\Windows\System32\GPOAdmin.dll
Report Id: a87fb79e-672e-4311-b356-b574aa4c2245
Faulting package full name:
Faulting package-relative application ID:
Faulting module name: GPOAdmin.dll, version: 10.0.14393.2068, time stamp: 0x5a7e7062
Exception code: 0xc0000005
Fault offset: 0x00000000000be1d6
Faulting process id: 0x3a8
Faulting application start time: 0x01d428f2d03e703a
Faulting application path: C:\Windows\system32\mmc.exe
Faulting module path: C:\Windows\System32\GPOAdmin.dll
Report Id: a87fb79e-672e-4311-b356-b574aa4c2245
Faulting package full name:
Faulting package-relative application ID:
↧
↧
Cannot RDP to Server. "This computer can't connect........"
Can't RDP to one of our server. Win 2008 R2 standard.
During attempt to connect by RDP, event log records this :
Schannel Event ID 36888 - The following fatal alert was generated: 10. The internal error state is 1203.
I've search the net and found some workarounds but nothing solved the issue. I also followed this KB article for checking but no luck.
https://support.microsoft.com/en-hk/help/2477176/troubleshoot-remote-desktop-disconnected-errors-in-windows-server-2008
Anyone have any idea? Thanks.
↧
Windows Server 2016 Event 10028, DistributedCOM DCOM was unable to communicate with the computer 8.8.8.8
DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID 484 (C:\Windows\system32\dcdiag.exe).
This occurred after DNS conditional forwarder was setup. In monitoring the tests pass.
↧
Could you please suggest for MEMORY.DMP that root cause and solution for resolve this problem
https://social.technet.microsoft.com/Forums/getfile/1297512
My Server run OS Windows Server2012 DATACENTER on VMware
Detail MEMORY.DMP as below
------------------------------------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: Server, suite: TerminalServer DataCenter SingleUserTS
Built by: 9600.17415.amd64fre.winblue_r4.141028-1500
Machine Name:
Kernel base = 0xfffff800`a1217000 PsLoadedModuleList = 0xfffff800`a14f0250
Debug session time: Sat Jul 14 04:04:21.551 2018 (UTC + 0:00)
System Uptime: 237 days 20:14:54.479
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
................................
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffffe001636e5880, 0, 0, 0}
Probably caused by : wininit.exe
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffe001636e5880, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
PROCESS_OBJECT: ffffe001636e5880
IMAGE_NAME: wininit.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: WmiPrvSE.exe
BUGCHECK_STR: 0xEF_WmiPrvSE.exe
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff800a1830d1c to fffff800a13679a0
STACK_TEXT:
ffffd000`b70c69a8 fffff800`a1830d1c : 00000000`000000ef ffffe001`636e5880 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`b70c69b0 fffff800`a178fd50 : ffffe001`636e5880 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspCatchCriticalBreak+0xa4
ffffd000`b70c69f0 fffff800`a1673295 : 0000003c`7cef5401 00000000`00000000 ffffe001`636e5880 ffffe001`636e5880 : nt! ?? ::NNGAKEGL::`string'+0x4aba0
ffffd000`b70c6a50 fffff800`a1673022 : ffffffff`ffffffff ffffe001`63533080 ffffe001`636e5880 ffffe001`661f3880 : nt!PspTerminateProcess+0xe5
ffffd000`b70c6a90 fffff800`a13731b3 : ffffe001`636e5880 ffffe001`661f3880 ffffd000`b70c6b80 0000003c`7cef2cd0 : nt!NtTerminateProcess+0x9e
ffffd000`b70c6b00 00007ff8`35d20f0a : 00007ff8`32fc9fa9 00000000`00000000 0000003c`00000000 00000000`00000230 : nt!KiSystemServiceCopyEnd+0x13
0000003c`7d07da38 00007ff8`32fc9fa9 : 00000000`00000000 0000003c`00000000 00000000`00000230 00000000`00000000 : ntdll!NtTerminateProcess+0xa
0000003c`7d07da40 00007ff8`2773db9e : 00000000`00000000 00007ff8`276f8c60 0000003c`7d07daf0 00000000`00000230 : KERNELBASE!TerminateProcess+0x25
0000003c`7d07da70 00007ff8`2773959c : 00000000`00000001 0000003c`7cef5180 0000003c`00000170 00007ff8`27873430 : cimwin32!Process::ExecTerminate+0x12e
0000003c`7d07dae0 00007ff8`29399cb9 : 00007ff8`2770b7c0 0000003c`7cef3df0 00007ff8`27873430 0000003c`7c6ae200 : cimwin32!Process::ExecMethod+0x2dddc
0000003c`7d07db20 00007ff8`293999bc : 0000003c`7cef5450 0000003c`7cef5180 0000003c`7c65f200 00000000`00000000 : framedynos!Provider::ExecMethod+0xb5
0000003c`7d07dba0 00007ff6`5568d2a9 : 0000003c`7c6676a0 0000003c`7c636930 0000003c`7c636920 0000003c`7c650678 : framedynos!CWbemProviderGlue::ExecMethodAsync+0x40c
0000003c`7d07e1c0 00007ff6`5568ce4f : 00000000`00000000 00007ff8`00000000 0000003c`7d07e301 00000000`00000000 : wmiprvse!CInterceptor_IWbemSyncProvider::Helper_ExecMethodAsync+0x3a9
0000003c`7d07e280 00007ff8`338b2053 : 0000003c`00000000 0000003c`7c65b1c8 0000003c`7c672198 00000000`00000000 : wmiprvse!CInterceptor_IWbemSyncProvider::ExecMethodAsync+0x13f
0000003c`7d07e350 00007ff8`338bc70d : 0000003c`7d07e7f0 00007ff8`2a8f1b82 0000003c`7c652658 00007ff8`33c688a0 : RPCRT4!Invoke+0x73
0000003c`7d07e3d0 00007ff8`33c6d58a : 0000003c`7c652658 00007ff8`338ca501 0000003c`7c652658 00000000`00000000 : RPCRT4!NdrStubCall2+0x35e
0000003c`7d07ea40 00007ff8`2b04b746 : 00007ff8`00000001 00007ff8`2a8f13a0 0000003c`7c650a78 00000000`00000000 : combase!CStdStubBuffer_Invoke+0xa0 [d:\9147\com\combase\ndr\ndrole\stub.cxx @ 1582]
0000003c`7d07ea80 00007ff8`33c686ad : 00007ff8`2b04b700 0000003c`7d07ed50 00000000`00000000 00000000`00000000 : FastProx!CBaseStublet::Invoke+0x46
0000003c`7d07eab0 00007ff8`33af4f5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : combase!SyncStubInvoke+0x205 [d:\9147\com\combase\dcomrem\channelb.cxx @ 1664]
0000003c`7d07ec50 00007ff8`33c6951f : 00000000`00000010 0000003c`7c652870 0000003c`7d07ef20 00000000`00000000 : combase!CCtxComChnl::ContextInvoke+0x27a [d:\9147\com\combase\dcomrem\ctxchnl.cxx @ 1377]
0000003c`7d07ee60 00007ff8`33c68fb0 : 0000003c`7c652170 0000003c`7c652170 0000003c`7d07f390 00007ff8`33c68dc9 : combase!AppInvoke+0x1af [d:\9147\com\combase\dcomrem\channelb.cxx @ 1481]
0000003c`7d07ef50 00007ff8`33c69b35 : 00000000`00000000 00000000`00070005 0000003c`7c63f510 00007ff8`35cbd773 : combase!ComInvokeWithLockAndIPID+0x676 [d:\9147\com\combase\dcomrem\channelb.cxx @ 2314]
0000003c`7d07f190 00007ff8`338b23c7 : 00000000`00000000 00007ff8`33c69cf0 00000000`00000000 0000003c`7c61cf90 : combase!ThreadInvoke+0x48a [d:\9147\com\combase\dcomrem\channelb.cxx @ 5488]
0000003c`7d07f260 00007ff8`338b2220 : 0000003c`7c661550 00000000`00000000 0000003c`7d07f420 0000003c`7c4a0cc0 : RPCRT4!DispatchToStubInCNoAvrf+0x33
0000003c`7d07f2b0 00007ff8`338c9a78 : 0000003c`7c661550 00000000`00000000 0000003c`00000000 0000003c`7c652ec0 : RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x190
0000003c`7d07f3b0 00007ff8`338b2c86 : 00000005`092e6d51 0000003c`7c652ec0 00000000`00000000 0000003c`7c652ec0 : RPCRT4!LRPC_SCALL::DispatchRequest+0x4c9
0000003c`7d07f4c0 00007ff8`338b2ad8 : 00000039`00000000 0000003c`7c652c10 0000003c`7c652ec0 00000000`00000000 : RPCRT4!LRPC_SCALL::HandleRequest+0x291
0000003c`7d07f570 00007ff8`338b18bd : 0000003c`7c63de30 0000003c`7d07f700 00007ff8`3390edbc 0000003c`7c63df38 : RPCRT4!LRPC_SASSOCIATION::HandleRequest+0x238
0000003c`7d07f600 00007ff8`338b16be : 0000003c`7c61cb58 0000003c`7c63df38 00000000`00000000 00007ff8`3390edbc : RPCRT4!LRPC_ADDRESS::ProcessIO+0x444
0000003c`7d07f740 00007ff8`35cc58f0 : 0000003c`7c618d20 0000003c`7c61cb10 00007ff8`338b1600 0000003c`7d07f7f8 : RPCRT4!LrpcIoComplete+0x144
0000003c`7d07f7e0 00007ff8`35cc3c28 : 00000000`00000000 00007ff8`35cc5600 00000000`00000000 0000003c`7c644750 : ntdll!TppAlpcpExecuteCallback+0x210
0000003c`7d07f850 00007ff8`35b413d2 : 00000000`00000000 00007ff8`35cc33a0 0000003c`7c618d20 00000000`00000000 : ntdll!TppWorkerThread+0x888
0000003c`7d07fc30 00007ff8`35d003c4 : 00007ff8`35b413b0 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x22
0000003c`7d07fc60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION:
FAILURE_BUCKET_ID: 0xEF_WmiPrvSE.exe_IMAGE_wininit.exe
BUCKET_ID: 0xEF_WmiPrvSE.exe_IMAGE_wininit.exe
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xef_wmiprvse.exe_image_wininit.exe
FAILURE_ID_HASH: {dd961e7f-9fb2-75de-5c19-5602ba5ccdd2}
Followup: MachineOwner
---------
↧