Author Topic: Windows Repair 4.4.7 - The app can not be repaired!  (Read 546 times)

0 Members and 1 Guest are viewing this topic.

Offline Angelika

  • Full Member
  • ***
  • Join Date: Feb 2017
  • Posts: 215
  • Karma: -1
    • View Profile
Windows Repair 4.4.7 - The app can not be repaired!
« on: April 07, 2019, 12:29:54 AM »
WR - The app can not be repaired!
Win 7
Nazwa aplikacji powodującej błąd: WmiPrvSE.exe, wersja: 10.0.10586.117, sygnatura czasowa: 0x56bf013f
Nazwa modułu powodującego błąd: CoreAgnt.dll_unloaded, wersja: 0.0.0.0, sygnatura czasowa: 0x5c1bf2c4
Kod wyjątku: 0xc0000005
Przesunięcie błędu: 0x000007fee81f7dc8
Identyfikator procesu powodującego błąd: 0xb98
Godzina uruchomienia aplikacji powodującej błąd: 0x01d4ed0edaa4a91d
Ścieżka aplikacji powodującej błąd: C:\Windows\System32\wbem\WmiPrvSE.exe
Ścieżka modułu powodującego błąd: CoreAgnt.dll
Identyfikator raportu: 7a0ad71e-5904-11e9-a0ca-0862662a261f




Code: [Select]
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Module load completed but symbols could not be loaded for WmiPrvSE.exe
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ncobjapi.dll -
Unable to load image CoreAgnt.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for CoreAgnt.dll
*** ERROR: Module load completed but symbols could not be loaded for CoreAgnt.dll

KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start
    Name: <blank>
    Time: 2019-04-07T07:19:00.732Z
    Diff: 402732 mSec

Timeline: Dump.Current
    Name: <blank>
    Time: 2019-04-07T07:12:18.0Z
    Diff: 0 mSec

Timeline: Process.Start
    Name: <blank>
    Time: 2019-04-07T06:55:15.0Z
    Diff: 1023000 mSec

Timeline: OS.Boot
    Name: <blank>
    Time: 2019-04-07T06:54:56.0Z
    Diff: 1042000 mSec


DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT:  (.ecxr)
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=00000000012afa78
rip=000007fee81f7dc8 rsp=00000000012af9e0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=000007fefd2010d8
r11=0000079300ae0076 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010200
CoreAgnt+0x77dc8:
000007fe`e81f7dc8 ??              ???
Resetting default scope

FAULTING_IP:
CoreAgnt.dll!Unloaded+77dc8
000007fe`e81f7dc8 ??              ???

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 000007fee81f7dc8 (CoreAgnt+0x0000000000077dc8)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 000007fee81f7dc8
Attempt to execute non-executable address 000007fee81f7dc8

DEFAULT_BUCKET_ID:  BAD_INSTRUCTION_PTR

FOLLOWUP_IP:
CoreAgnt.dll!Unloaded+77dc8
000007fe`e81f7dc8 ??              ???

EXECUTE_ADDRESS: 7fee81f7dc8

FAILED_INSTRUCTION_ADDRESS:
CoreAgnt.dll!Unloaded+77dc8
000007fe`e81f7dc8 ??              ???

ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  000007fee81f7dc8

WATSON_BKT_PROCSTAMP:  56bf013f

WATSON_BKT_PROCVER:  10.0.10586.117

PROCESS_VER_PRODUCT:  Microsoft® Windows® Operating System

WATSON_BKT_MODULE:  unknown

WATSON_BKT_MODVER:  0.0.0.0

WATSON_BKT_MODOFFSET:  e81f7dc8

BUILD_VERSION_STRING:  6.1.7601.24388 (win7sp1_ldr_escrow.190311-1905)

MODLIST_WITH_TSCHKSUM_HASH:  ef6919961c9eb847aa75fa4e2ea8e82ff0c08af3

MODLIST_SHA1_HASH:  a5e6c187e975f46691f8d591620b99a12e744bb8

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

PRODUCT_TYPE:  1

SUITE_MASK:  272

DUMP_FLAGS:  d96

DUMP_TYPE:  0

PROCESS_NAME:  unknown

ANALYSIS_SESSION_HOST:  KOMPUTER

ANALYSIS_SESSION_TIME:  04-07-2019 09:19:00.0732

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

THREAD_ATTRIBUTES:
OS_LOCALE:  PLK

BUGCHECK_STR:  APPLICATION_FAULT_BAD_INSTRUCTION_PTR_SOFTWARE_NX_FAULT_INVALID_POINTER_EXECUTE

PRIMARY_PROBLEM_CLASS:  APPLICATION_FAULT

PROBLEM_CLASSES:

    ID:     [0n313]
    Type:   [@ACCESS_VIOLATION]
    Class:  Addendum
    Scope:  BUCKET_ID
    Name:   Omit
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0xc08]
    Frame:  [0] : CoreAgnt.dll!Unloaded

    ID:     [0n287]
    Type:   [INVALID_POINTER_EXECUTE]
    Class:  Primary
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0xc08]
    Frame:  [0] : CoreAgnt.dll!Unloaded

    ID:     [0n295]
    Type:   [SOFTWARE_NX_FAULT]
    Class:  Primary
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [0xb98]
    TID:    [0xc08]
    Frame:  [0] : CoreAgnt.dll!Unloaded

    ID:     [0n296]
    Type:   [BAD_INSTRUCTION_PTR]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [0xb98]
    TID:    [0xc08]
    Frame:  [0] : CoreAgnt.dll!Unloaded

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 000007fee81f7dc8

STACK_TEXT: 
00000000`012af9e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : CoreAgnt+0x77dc8


THREAD_SHA1_HASH_MOD_FUNC:  5d028f64e3909d2ad74b8fb982f9036aa97531fd

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c4b4f1f6823eb837ec0b5a2fc0a9d950e90c5b31

THREAD_SHA1_HASH_MOD:  7bf4e5aa7b0a035cb58cdc86181a7273d2a83a11

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  CoreAgnt.dll!Unloaded+77dc8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CoreAgnt

IMAGE_NAME:  CoreAgnt.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  5c1bf2c4

STACK_COMMAND:  ~4s ; .ecxr ; kb

FAILURE_BUCKET_ID:  BAD_INSTRUCTION_PTR_c0000005_CoreAgnt.dll!Unloaded

BUCKET_ID:  X64_APPLICATION_FAULT_BAD_INSTRUCTION_PTR_SOFTWARE_NX_FAULT_INVALID_POINTER_EXECUTE_BAD_IP_CoreAgnt.dll!Unloaded+77dc8

FAILURE_EXCEPTION_CODE:  c0000005

FAILURE_IMAGE_NAME:  CoreAgnt.dll

BUCKET_ID_IMAGE_STR:  CoreAgnt.dll

FAILURE_MODULE_NAME:  CoreAgnt

BUCKET_ID_MODULE_STR:  CoreAgnt

FAILURE_FUNCTION_NAME:  Unloaded

BUCKET_ID_FUNCTION_STR:  Unloaded

BUCKET_ID_OFFSET:  77dc8

BUCKET_ID_MODTIMEDATESTAMP:  5c1bf2c4

BUCKET_ID_MODCHECKSUM:  0

BUCKET_ID_MODVER_STR:  0.0.0.0

BUCKET_ID_PREFIX_STR:  X64_APPLICATION_FAULT_BAD_INSTRUCTION_PTR_SOFTWARE_NX_FAULT_INVALID_POINTER_EXECUTE_BAD_IP_

FAILURE_PROBLEM_CLASS:  APPLICATION_FAULT

FAILURE_SYMBOL_NAME:  CoreAgnt.dll!Unloaded

TARGET_TIME:  2019-04-07T07:12:18.000Z

OSBUILD:  7601

OSSERVICEPACK:  24388

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) SingleUserTS

USER_LCID:  0

OSBUILD_TIMESTAMP:  2019-03-12 05:16:34

BUILDDATESTAMP_STR:  190311-1905

BUILDLAB_STR:  win7sp1_ldr_escrow

BUILDOSVER_STR:  6.1.7601.24388

ANALYSIS_SESSION_ELAPSED_TIME:  1653

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:bad_instruction_ptr_c0000005_coreagnt.dll!unloaded

FAILURE_ID_HASH:  {f00aa262-5c6d-2008-8027-e22d2939859b}

Followup:     MachineOwner


« Last Edit: April 07, 2019, 12:33:43 AM by Angelika »

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 8347
  • Location: UK
  • Karma: 114
    • View Profile
Re: Windows Repair 4.4.7 - The app can not be repaired!
« Reply #1 on: April 07, 2019, 01:17:37 AM »
I've used Google Translate to translate your main error message should I need to refer this to Shane.

The name of the application causing the error: WmiPrvSE.exe, version: 10.0.10586.117, timestamp: 0x56bf013f
The name of the module causing the error: CoreAgnt.dll_unloaded, version: 0.0.0.0, timestamp: 0x5c1bf2c4
Exception code: 0xc0000005
Error offset: 0x000007fee81f7dc8
The identifier of the process causing the error: 0xb98
The time the application started causing the error: 0x01d4ed0edaa4a91d
The application path causing the error: C: \ Windows \ System32 \ wbem \ WmiPrvSE.exe
The path of the module causing the error: CoreAgnt.dll

The rest of the error in conjunction with that would seem to point to a bad instruction with the repair program applying a Win 10 instruction on a Win 7 system.

I'm currently preparing a Win 10 machine for a test run of 4.4.7 but will prepare my Win 7 machine to see if I get the same error and get back to you on this.
Tom.

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 8347
  • Location: UK
  • Karma: 114
    • View Profile
Re: Windows Repair 4.4.7 - The app can not be repaired!
« Reply #2 on: April 07, 2019, 04:32:22 AM »
I first ran 4.4.6 and then 4.4.7 on my Win 7 machine and the repairs completed both times without getting the error you have experienced, although the WMI repair logs did show some errors as you can see from the attached logs which appear to look the same.

Did the repair program hang for you on that repair and was there a particular reason why you ran the repair program ?

Can you run a sfc /scannow to see if it reports anything untoward and then try 4.4.7 again to see if you get the same error.
Tom.

Offline Angelika

  • Full Member
  • ***
  • Join Date: Feb 2017
  • Posts: 215
  • Karma: -1
    • View Profile
Re: Windows Repair 4.4.7 - The app can not be repaired!
« Reply #3 on: April 08, 2019, 07:24:49 AM »
SFC /SCANNOW - Always shows that everything is OK!
WR in any version can not fix many problems, and it will not fix it, even though it has such repair options. The error was, is and still will probably remain, and occurs from time to time at an unexpected moment.
But as I can see that many users publish similar errors on different websites and there are no final solutions.

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 8347
  • Location: UK
  • Karma: 114
    • View Profile
Re: Windows Repair 4.4.7 - The app can not be repaired!
« Reply #4 on: April 08, 2019, 07:37:14 AM »
Have a read through this article and try the bottom set of cmds after creating a restore point and then you can see if the repair program still reports that error.

https://blogs.technet.microsoft.com/yongrhee/2016/06/23/wmi-stop-hurting-yourself-by-using-for-f-s-in-dir-s-b-mof-mfl-do-mofcomp-s/
Tom.

Offline Angelika

  • Full Member
  • ***
  • Join Date: Feb 2017
  • Posts: 215
  • Karma: -1
    • View Profile
Re: Windows Repair 4.4.7 - The app can not be repaired!
« Reply #5 on: April 08, 2019, 10:02:15 AM »
But I do not have a damaged WMI, as indicated by various special diagnostic tools. So in this case, it's not recommended, because the result will be the same.
My problem only affects the error in CoreAgnt.dll
BAD_INSTRUCTION_PTR_c0000005_CoreAgnt.dll!Unloaded
Of course, it is not damaged, but for some reason you can not load this module correctly.

Offline satrow

  • Full Member
  • ***
  • Join Date: Nov 2016
  • Posts: 120
  • Location: Cymru
  • Karma: 3
    • View Profile
Re: Windows Repair 4.4.7 - The app can not be repaired!
« Reply #6 on: April 08, 2019, 11:22:46 AM »
c0000005 indicates a memory access violation, so it looks like the instruction to CoreAgnt.dll failed because CoreAgnt.dll was no longer loaded, or possibly loaded in a different memory location.

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 8347
  • Location: UK
  • Karma: 114
    • View Profile
Re: Windows Repair 4.4.7 - The app can not be repaired!
« Reply #7 on: April 08, 2019, 02:47:31 PM »
But I do not have a damaged WMI, as indicated by various special diagnostic tools. So in this case, it's not recommended, because the result will be the same.
My problem only affects the error in CoreAgnt.dll
BAD_INSTRUCTION_PTR_c0000005_CoreAgnt.dll!Unloaded
Of course, it is not damaged, but for some reason you can not load this module correctly.

Are there any other symptoms or correlating errors in Event Viewer ?
Tom.

Offline hellowdave

  • Newbie
  • *
  • Join Date: Apr 2019
  • Posts: 1
  • Karma: 0
    • View Profile
Re: Windows Repair 4.4.7 - The app can not be repaired!
« Reply #8 on: April 17, 2019, 08:37:46 AM »
HELP!

Updated to 4.7, and the program will open, do the Backup, but when I click to Start Repairs it just closes.

This is the PRO version - Is there any way to Roll Back to the previous version until this is fixed?

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 8347
  • Location: UK
  • Karma: 114
    • View Profile
Re: Windows Repair 4.4.7 - The app can not be repaired!
« Reply #9 on: April 17, 2019, 08:43:09 AM »
You should really have opened your own thread for this but I've test run 4.4.7 and it worked fine for me.

Are you running the program in Safe Mode with Networking ?

If you are then try reinstalling the program.

What is the reason why you need to run the repair program ?
Tom.