Author Topic: 0x80244019 WU_E_PT_HTTP_STATUS_NOT_FOUND  (Read 18541 times)

0 Members and 1 Guest are viewing this topic.

makinero

  • Guest
0x80244019 WU_E_PT_HTTP_STATUS_NOT_FOUND
« on: July 22, 2016, 10:44:24 am »
WR 3.9.x does not repair
  only cause changes in the system and complicated problems.
Eg. File & Permissions Register System Files & Reset Service Permission
causing a variety of errors ... A complete mess in the system.
Very complicated complex errors that probably very hard to diagnose and fix.
Access Errors, errors installers, No access for some files or folders in the Operational sytemie and much more!
Can I undo the changes, but then the tool is not useful for anything when not working well?
« Last Edit: July 23, 2016, 06:41:05 am by ▒ »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: WR = devastating repair!
« Reply #1 on: July 22, 2016, 01:42:14 pm »
Boot back into Safe Mode, open WR and use Option 5 to restore the registry.

Use the dropdown to select a date if the box is clear.

I'll let Shane know.

makinero

  • Guest
Re: WR = devastating repair!
« Reply #2 on: July 22, 2016, 02:11:08 pm »

If restore the registry to get series of other errors especially affect applications since restoring Remove also good, new entries.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: WR = devastating repair!
« Reply #3 on: July 22, 2016, 02:12:12 pm »
Don't know what you mean by that.

makinero

  • Guest
Re: WR = devastating repair!
« Reply #4 on: July 23, 2016, 02:26:11 am »
Boggin - If you restore the registry, some programs /apps will not work or will notify various ERRORS or incorrect settings, or corrupted to the installation, so restore the registry was ALWAYS risk!
but no one understands and believes that restore the registry and again everything will work on 100% = complete nonsense

WR If use one or all Option Repair "Permissions
01
02
03"




WR 3.9.4 or 3.9.5 = BUG ACL



Determine whether we are on an 32 or 64 bit machine


LookupAccountName : HKEY_LOCAL_MACHINE:administrators 1337 Struktura identyfikatora zabezpieczenia jest nieprawidłowa.

Current object HKEY_LOCAL_MACHINE will not be processed


Elapsed Time: 00 00:00:00
Done:        0, Modified        0, Failed        0, Syntax errors        1
Last Syntax Error:WARNING : /grant=administrators=f : Error when checking arguments - HKEY_LOCAL_MACHINE
LookupAccountName : HKEY_CURRENT_USER:administrators 1337 Struktura identyfikatora zabezpieczenia jest nieprawidłowa.

Current object HKEY_CURRENT_USER will not be processed


Elapsed Time: 00 00:00:00
Done:        0, Modified        0, Failed        0, Syntax errors        1
Last Syntax Error:WARNING : /grant=administrators=f : Error when checking arguments - HKEY_CURRENT_USER
LookupAccountName : HKEY_CLASSES_ROOT:administrators 1337 Struktura identyfikatora zabezpieczenia jest nieprawidłowa.

Current object HKEY_CLASSES_ROOT will not be processed


Elapsed Time: 00 00:00:00
Done:        0, Modified        0, Failed        0, Syntax errors        1
Last Syntax Error:WARNING : /grant=administrators=f : Error when checking arguments - HKEY_CLASSES_ROOT
LookupAccountName : C:\Windows:administrators 1337 Struktura identyfikatora zabezpieczenia jest nieprawidłowa.

Current object C:\Windows will not be processed


Elapsed Time: 00 00:00:00
Done:        0, Modified        0, Failed        0, Syntax errors        1
Last Syntax Error:WARNING : /grant=administrators=f : Error when checking arguments - C:\Windows
FINISHED.

Press any key to exit . . .
« Last Edit: July 23, 2016, 02:54:12 am by ▒ »

Offline Still_Game

  • Full Member
  • ***
  • Join Date: Sep 2015
  • Posts: 208
  • Location: France
  • Karma: 12
    • View Profile
Re: WR = devastating repair!
« Reply #5 on: July 23, 2016, 03:21:04 am »
OP - I must be exceptionally lucky then - done it quite a few times and I can't think of any time that restoring the registry hasn't worked for me in Windows 7.
Iain

ThinkPad T450s W10 Pro x64
Windows Defender, Malwarebytes Premium
Macrium Reflect 7 Home, Tweaking WRAIO Pro

makinero

  • Guest
Re: WR = devastating repair!
« Reply #6 on: July 23, 2016, 04:11:00 am »
@echo off
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f /grant=system=f
subinacl /subdirectories %windir% /grant=administrators=f /grant=system=f
@Echo =========================
@Echo Finished.
@Echo =========================
@pause

-----------------------------------------------------------------------------------------------------------
@echo off
title Resetting ACLs…

setlocal

echo.
echo Determine whether we are on an 32 or 64 bit machine
echo.

if “%PROCESSOR_ARCHITECTURE%”==”x86” if “%PROCESSOR_ARCHITEW6432%”==”” goto x86

set ProgramFilesPath=%ProgramFiles(x86)%

goto startResetting

:x86

set ProgramFilesPath=%ProgramFiles%

:startResetting

echo.

if exist “%ProgramFilesPath%\Windows Resource Kits\Tools\subinacl.exe” goto filesExist

echo ***ERROR*** – Could not find file %ProgramFilesPath%\Windows Resource Kits\Tools\subinacl.exe. Double-check that SubInAcl is correctly installed and re-run this script.
goto END

:filesExist

pushd “%ProgramFilesPath%\Windows Resource Kits\Tools”

echo.
echo Resetting ACLs…
echo (this may take several minutes to complete)
echo.
echo IMPORTANT NOTE: For this script to run correctly, you must change
echo the values named YOURUSERNAME to be the Windows user account that
echo you are logged in with.
echo.
echo ==========================================================================
echo.
echo.
subinacl.exe /subkeyreg HKEY_CURRENT_USER /grant=administrators=f /grant=system=f /grant=restricted=r /grant=YOURUSERNAME=f /setowner=administrators > %temp%\subinacl_output.txt
echo.
echo.
subinacl.exe /keyreg HKEY_CURRENT_USER /grant=administrators=f /grant=system=f /grant=restricted=r /grant=YOURUSERNAME=f /setowner=administrators >> %temp%\subinacl_output.txt
echo.
echo.
subinacl.exe /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f /grant=system=f /grant=users=r /grant=everyone=r /grant=restricted=r /setowner=administrators >> %temp%\subinacl_output.txt
echo.
echo.
subinacl.exe /keyreg HKEY_LOCAL_MACHINE /grant=administrators=f /grant=system=f /grant=users=r /grant=everyone=r /grant=restricted=r /setowner=administrators >> %temp%\subinacl_output.txt
echo.
echo.
subinacl.exe /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f /grant=system=f /grant=users=r /setowner=administrators >> %temp%\subinacl_output.txt
echo.
echo.
subinacl.exe /keyreg HKEY_CLASSES_ROOT /grant=administrators=f /grant=system=f /grant=users=r /setowner=administrators >> %temp%\subinacl_output.txt
echo.
echo.
echo System Drive…
subinacl.exe /subdirectories %ProgramFilesPath%\ /grant=administrators=f /grant=system=f /grant=users=e >> %temp%\subinacl_output.txt
echo.
echo.
echo Windows Directory…
subinacl.exe /subdirectories %windir%\ /grant=administrators=f /grant=system=f /grant=users=e >> %temp%\subinacl_output.txt
echo.
echo.
echo ==========================================================================
echo.
echo FINISHED.
echo.
echo Press any key to exit . . .
pause >NUL

popd

:END

endlocal
« Last Edit: July 23, 2016, 04:21:12 am by ▒ »

makinero

  • Guest
Re: WR = devastating repair!
« Reply #7 on: July 23, 2016, 04:59:14 am »
Boot back into Safe Mode, open WR and use Option 5 to restore the registry.

Why do I now have hundreds of bugs in the system when I restored the registry.
Problems with services, registry, folders, unable to access, environments, hundreds of problems ...
It is impossible now to fix it?

Offline Samson

  • Hero Member
  • *****
  • Join Date: Nov 2011
  • Posts: 915
  • Location: London
  • Karma: 38
    • View Profile
Re: WR = devastating repair!
« Reply #8 on: July 23, 2016, 05:02:25 am »
Given the increasing list of problems that you have, then backing up your data and reinstalling the OS would be the the quickest and most likely successful resolution.

Personally, I would have been looking at a factory reset in the rear view mirror a fair few miles back down the road.

makinero

  • Guest
Re: WR = devastating repair!
« Reply #9 on: July 23, 2016, 05:30:28 am »
And you wondered what caused the problem?


The problem is WR,

Why Author WR release upgrades?
Because the fixes previous bugs.
But if you use prev version WR bugs still exist in the system due to a previous version of the WR.
So I expect that now WR latest version will fix bugs in the system caused by an old version !!! I am asking !!!!

----------------------------------------------
I'm using version 3.9.4 and cause bug.
Now version 3.9.5 does not fix the bug that existed in version 3.9.4

Updated Tweaking.com - ManageACL to v1.3.0

Updated Tweaking.com - Registry Backup to v3.5.0

Large amounts of code changes, improvements and bug fixes.



« Last Edit: July 23, 2016, 05:52:54 am by ▒ »

makinero

  • Guest
Re: WR = devastating repair!
« Reply #10 on: July 23, 2016, 06:18:55 am »
Given the increasing list of problems that you have, then backing up your data and reinstalling the OS would be the the quickest and most likely successful resolution.

Personally, I would have been looking at a factory reset in the rear view mirror a fair few miles back down the road.

  + ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx <====NOT WORK
This is a Windows© Communication Foundation service.

Metadata publishing for this service is currently disabled.

2016-07-23   12:30:22:722    836   1364   AU   ###########  AU: Uninitializing Automatic Updates  ###########
2016-07-23   12:30:22:722    836   dbc   Agent     * WARNING: Failed to filter search results, error = 0x8024000B
2016-07-23   12:30:22:722    836   dbc   Agent   *********
2016-07-23   12:30:22:722    836   dbc   Agent   **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2016-07-23   12:30:22:722    836   dbc   Agent   *************
2016-07-23   12:30:22:779    836   1364   Service   *********
2016-07-23   12:30:22:779    836   1364   Service   **  END  **  Service: Service exit [Exit code = 0x240001]

debug 2:


Message: Windows Update can not find an update, because an error occurred 0x80244019.
0x80244019 WU_E_PT_HTTP_STATUS_NOT_FOUND Same as HTTP status 404 - the server cannot find the requested URI (Uniform Resource Identifier)
« Last Edit: July 23, 2016, 06:40:17 am by ▒ »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: 0x80244019 WU_E_PT_HTTP_STATUS_NOT_FOUND
« Reply #11 on: July 23, 2016, 07:17:59 am »
Are you saying that your machine was okay prior to running 3.9.4 or had you been tinkering with it and forgot where the bits went back and expected 3.9.4 to fix it ?

Personally, I'm with Samson on this - factory reset or repair/reinstall.


makinero

  • Guest
Re: 0x80244019 WU_E_PT_HTTP_STATUS_NOT_FOUND
« Reply #12 on: July 23, 2016, 08:03:12 am »
Are you kidding? You really kidding!!!
Fix the application WR 3.9.5, which causes the problems mentioned above!

What causes problems WR 3.9.5 I chose mostly all repair options and result in:
1.
Code: [Select]
Nie można wygenerować kontekstu aktywacji dla "C:\Users\MOJA\Downloads\vcredist_arm.exe". Nie można odnaleźć zestawu zależnego Microsoft.Windows.Common-Controls,language="&#x2a;",processorArchitecture="arm",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0". Użyj narzędzia sxstrace.exe, aby uzyskać szczegółową diagnozę.
2.
Code: [Select]
Błąd Usługi kopiowania woluminów w tle: nieoczekiwany błąd podczas badania interfejsu IVssWriterCallback. hr = 0x80070005, Odmowa dostępu.
. To jest często spowodowane przez niepoprawne ustawienia zabezpieczeń w procesie zapisującym lub żądającym.

Operacja:
   Zbieranie danych modułu zapisującego

Kontekst:
   Identyfikator klasy modułu zapisującego: {e8132975-6f93-4464-a53e-1050253ae220}
   Nazwa modułu zapisującego: System Writer
   Identyfikator wystąpienia modułu zapisującego: {905dfe3b-d483-46b0-82f0-8e8e92e47f8a}
3.
Code: [Select]
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_64) - Tried to start a service that wasn't the latest version of CLR Optimization service. Will shutdown
4.
Code: [Select]
Nie można zainstalować ciągów liczników wydajności dla usługi .NET CLR Networking 4.0.0.0 (). Pierwszy wpis DWORD w sekcji danych (Data) zawiera kod błędu.
5. More...


WR 3.9.5 bug !!! (PLEASE TEST ALL OPTION ~33 REPAIR !!!!!!!!!!!!!!!!!!!)


SAFE MODE RUN WR
Log contains MANY ERROR /WARNING

mini-example: (because big log, many error)
Code: [Select]
ERROR: Writing SD to <\\?\C:\Windows> failed with: Odmowa dostępu.
ERROR: Writing SD to <\\?\C:\Windows\addins> failed with: Odmowa dostępu.
ERROR: Writing SD to <\\?\C:\Windows\addins\FXSEXT.ecf> failed with: Odmowa dostępu.
ERROR: Writing SD to <\\?\C:\Windows\AppPatch> failed with: Odmowa dostępu.
ERROR: Writing SD to <\\?\C:\Windows\AppPatch\AcGenral.dll> failed with: Odmowa dostępu.
ERROR: Writing SD to <\\?\C:\Windows\AppPatch\AcLayers.dll> failed with: Odmowa dostępu.


50000+ ERROR !!!!!
Errors caused by using all the OPTION for repair
« Last Edit: July 23, 2016, 08:15:05 am by ▒ »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: 0x80244019 WU_E_PT_HTTP_STATUS_NOT_FOUND
« Reply #13 on: July 23, 2016, 08:15:57 am »
You are the only one who has complained of these errors - what else have you done to your system prior to running WR ?

I think you have been given the best advice in the circumstances - bite the bullet and factory reset - but it's up to you.

makinero

  • Guest
Re: 0x80244019 WU_E_PT_HTTP_STATUS_NOT_FOUND
« Reply #14 on: July 23, 2016, 08:20:02 am »
I did nothing but ONLY experimented with 30 - 33 settings (Windows Repairs)
And it caused all the errors in the system: D
Experimented? ---> I was looking for bugs and this caused possibly 100,000+ errors (!) Really.

Run SAFE MODE WR 3.9.5 and test !!!


« Last Edit: July 23, 2016, 08:23:10 am by ▒ »