Messages

1

Tweaking.com Support & Help / Re: Install problem resolution

« on: June 14, 2019, 01:47:55 pm »

Well, that link sure provides what seems like a complete and comprehensive checklist for a deep dive into the OS innards to effect (perhaps) a fix, so a bit more time than I've got at present and will set it aside for a later time by just performing a safe-mode reboot for future Tweaking installs as the lazy approach.  Thanks very much, regardless!

2

Tweaking.com Support & Help / Re: Install problem resolution

« on: June 14, 2019, 11:09:18 am »

There are 3 yellow-icon warnings in the event viewer application group, with this explanation: "Profile notification of event Load for component {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB} failed, error code is See Tracelogging for error details."  Not particularly helpful, but the entry does point to SYSTEM as the user.

In the SYSTEM group, there are errors at a comparable (but not identical) time-stamp for "Event 10016, Distributed DCOM"  which provide this general description:

"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user RIVENDELL2\James Vance SID (S-1-5-21-3774824159-2135294730-2250967024-1002) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The detailed description for that same event in friendly mode provides this:

- System

  - Provider

   [ Name]  Microsoft-Windows-DistributedCOM
   [ Guid]  {1B562E86-B7AA-4131-BADC-B6F3A001407E}
   [ EventSourceName]  DCOM
 
  - EventID 10016

   [ Qualifiers]  0
 
   Version 0
 
   Level 2
 
   Task 0
 
   Opcode 0
 
   Keywords 0x8080000000000000
 
  - TimeCreated

   [ SystemTime]  2019-06-14T17:28:28.935986400Z
 
   EventRecordID 25718
 
   Correlation
 
  - Execution

   [ ProcessID]  1556
   [ ThreadID]  2432
 
   Channel System
 
   Computer Rivendell2
 
  - Security

   [ UserID]  S-1-5-21-3774824159-2135294730-2250967024-1002
 

- EventData

  param1 application-specific
  param2 Local
  param3 Activation
  param4 {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
  param5 {15C20B67-12E7-4BB6-92BB-7AFF07997402}
  param6 RIVENDELL2
  param7 James Vance
  param8 S-1-5-21-3774824159-2135294730-2250967024-1002
  param9 LocalHost (Using LRPC)
  param10 Unavailable
  param11 Unavailable

------------------------------------

Insofar as an installation log for v4.5.2, I can't find one -- it's occurred to me they may not be created when in safe mode, but don't know.  Under the setup group of logs, the last of those dates from Patch Tuesday a few days ago.

3

Tweaking.com Support & Help / Re: Install problem resolution

« on: June 14, 2019, 08:03:09 am »

Well, there's progress of a sort -- on the W10H machine which originally had the install block that appeared to have been resolved, an error message appeared again when attempting to install v4.5.2 in normal mode.  While I rebooted that machine into safe mode w/networking, I installed the new tool without hiccups or issues on a different Win10H laptop which had never exhibited the install issue earlier; it did not arise now as the new software version installed properly in normal mode.  Once the other machine had finished booting into safe mode, the new version installed without problems on it as well.  I guess from now on, I'll just have to follow that protocol with installation of new Tweaking versions on the wonky machine as a less-PITA approach by comparison with wasting a lot more time trying to figure out why the install app doesn't like its normal OS mode.

4

Tweaking.com Support & Help / Re: 4.4.7 installation issue

« on: June 12, 2019, 02:54:40 pm »

This thread has been superceded, and is resolved in a later posting here: https://www.tweaking.com/forums/index.php/topic,6201.0.html

5

Tweaking.com Support & Help / Re: Install problem resolution

« on: June 12, 2019, 02:52:53 pm »

I wonder why 4.5.1 wouldn't install in normal mode.

I'm not certain, but I think since I had not resolved the basic problem underlying everything, I didn't give it the chance -- when I had downloaded the installer, I eventually rebooted into safe mode and did it that way.  I'll try to install in normal mode first with the next update, and I'll make an addition to the old thread which links to this one, and you can lock it again afterwards as closed.

6

Tweaking.com Support & Help / Re: Install problem resolution

« on: June 12, 2019, 01:59:45 pm »

Sorry, I wasn't complete in the description of how interim build installations actually went -- once I got 4.4.8 installed in safe mode and ran it, I tried the next update (4.4.9, I guess) in normal mode and it worked in normal mode, as did 4.5.0.  With 4.5.1 though, I discovered it had gone back to bad behavior and I relied on the workaround to get it installed.  I'll see what behavior occurs with the next release, as the fix described should have resolved it more permanently (at least until an MS update farkles it again).

7

Tweaking.com Support & Help / Install problem resolution

« on: June 12, 2019, 01:12:57 pm »

Some time back, I created a now-locked thread (https://www.tweaking.com/forums/index.php/topic,6083.0.html) with a temporary resolution for installing the Tweaking tool by booting into safe mode to accomplish that task successfully, but as the workaround wouldn't enable my Acronis TrueImage app to install in safe mode I had not completed a backup; that changed earlier today and the resolution may help someone else with comparable installation problems.

This started when I had become frustrated with the various "help" offerings through MS or most of the other sites which were identified in searches on the original error message, and life intervened in the form of chores and weather to distract me until this morning.  A new update for Skype today wouldn't install in a similar manner, but presented a different style and form of error message ("Access is denied" referencing "error 5")  -- another search with the combination brought up many of the same threads and posts as earlier, but also one reference to the MS KB article linked below, which revealed the problem lay somewhere in the permissions for vital folders being "read-only" as the installation process requires writing to such a folder.  The solution is to select the critical TEMP folders and toggle the top folder's properties "read-only" feature on and off, choosing the option to apply the action to all files and folders below; one may be under the root drive C:\ and the other under the relevant Windows\USERS\***\AppData\Local\Temp path.

https://support.microsoft.com/en-us/help/2623670/access-denied-or-other-errors-when-you-access-or-work-with-files-and-f

After I took that action for both folder lines and rebooted, I re-attempted the Skype update; it ran through fine, so I launched the TrueImage installation again and it ran through to completion.  Once I got the product activated and an initial backup performed, I went to their user forum to report the method of fixing the related installation errors and have now come here to report on the resolution.  I'll have to wait to test it against a new release of the Tweaking tool, and will report the outcome at that point in an update to this post if it remains unlocked.

8

Tweaking.com Support & Help / Re: 4.4.7 installation issue

« on: May 07, 2019, 11:41:29 am »

Thanks -- That's what I'm going to do more seriously, but after I logged in there and scanned over it last night to search threads for the term "permissions", none of the initial results were that relevant and I decided to back-burner the matter until I could explore it further and submit a coherent query to that forum.

9

Tweaking.com Support & Help / Re: 4.4.7 installation issue

« on: May 07, 2019, 08:46:02 am »

I forgot to say before that when I successfully installed v4.4.8 earlier this morning, it was done in normal mode rather than the safe mode w/networking approach which the previous release had required.  I had first attempted to install Acronis True Image in normal mode several weeks ago after the TwAIO issue was resolved, and when I got the permissions block I thought I'd try it with the other boot option as well -- unfortunately, its installer process requires normal mode to establish and start its requisite services so the installation process aborts.  I'll dig into whatever its issues are over the next week or so when I get the time, but I put the blame squarely on the UAC function (which I detest but hate to screw with blindly because of the other issues that can produce).

10

Tweaking.com Support & Help / Re: 4.4.7 installation issue

« on: May 07, 2019, 07:04:48 am »

I never followed up on your suggestions because of the stormy weather we've had in Central Texas the past couple of weeks, but when I checked this morning and found that v4.4.8 had been released I jumped that shark and decided to test if the problem would recur with the new release.  The good news is that whatever may have been the issue with v4.4.7, it did not occur with v4.4.8 -- it installed with no objections.

Now, if I can just figure out why I'm still getting a similar permissions block in my attempts to install Acronis True Image on that machine, I'd really be a happy camper.

11

Tweaking.com Support & Help / Re: 4.4.7 installation issue

« on: April 25, 2019, 03:04:48 pm »

Thanks -- I've never before needed to install an app in safe mode just for it to even launch (and I've been working with computers in various forms since the late 1960s), but that approach finally worked for both those Win10H machines, and I've since run the tool on each with no problems or hiccups.  I'll wait to see how the OS on each machine reacts to launch of the next version update, but for now all seems resolved.

12

Tweaking.com Support & Help / 4.4.7 installation issue

« on: April 22, 2019, 03:47:48 pm »

I downloaded the full installer for v4.4.7 both here and from Major Geeks, but can't get it to install on either of my Win10Hx64 machines although it installed without issue on a Win7Ultx64 machine.  A post-launch popup window declares that "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."  That message box refers to "C:\\Users\*****\AppData\Local\Temp\_ir_sf_temp0\irsetup.exe", but I've checked in Windows Explorer and the file exists at that location.  I've not only run the installer from right-clicking Start|Run and drilling down to choose the installer, but I've also right-clicked on that file in Explorer and selected the "Run as Administrator" option, but both produce the same error message.

Frustrating, and I'm wondering if this behavior might be related to the farkling which v4.4.1 gave the OS in both of those machines several months ago (there's a earlier thread in the forum on that set of issues).  On one machine, the SFC and DISM repairs then were able to recover its function, but on the other I was forced to reinstall the OS from the original image and then reload and rebuild everything to current status over the following week (so a PITA, in other words).

I never had any problems with the AIO tool before v4.4.1, and while I've installed newer version updates after the recovery on all of them, I have not run the newer tool(s) on any machine as I was hesitant to go through that repair/rebuild process again this quickly.  This latest AOI foible doesn't provide a lot of assurance that it won't occur again, but resetting all of the permissions manually isn't something I've got time to do just now.  Hopefully there's a simple (and safe) fix.

13

Tweaking.com Support & Help / Re: Windows 10 Won't Update

« on: February 05, 2019, 12:02:11 pm »

If you are still having problems, use the creation tool to make a bootable USB drive (16 Gb minimum) with the latest 1809 version on it, then use Windows Explorer to view the file contents of that USB drive; right-click on the setup.exe file and choose "Run as administrator".  If that also fails (with the same or a different error message), reboot and try it again by the self-initiating process; if that also fails, taking the image to some point even further back may be required.

14

Tweaking.com Support & Help / Re: Running v4.4.1 farkles Windows Update on Win10 w/ 0x80070643 error

« on: February 05, 2019, 11:53:19 am »

I have turned off hibernation now, thanks.

15

Tweaking.com Support & Help / Re: Running v4.4.1 farkles Windows Update on Win10 w/ 0x80070643 error

« on: February 04, 2019, 02:03:31 pm »

Well, this issue is now resolved so the thread can be closed.

No matter how I approached the repair or upgrade process, none of the usual avenues would allow the 1809 upgrade installation to proceed because of storage space limitations it perceived even if I was doing it from a USB and launched the 1809 setup.exe directly under an administrator account.  So, having a USB drive of the original out-of-box image and learning that the 1809 upgrade would apply to all previous versions of Windows 10, I simply nuked the laptop with the original image -- after it rebooted and walked me through the initial setup of user accounts, I proceeded to immediately rebuild its fresh OS with application of the 1809 upgrade.  That has proven successful, and I've since run the built-in cleaners to remove unneeded storage, and jettisoned the old Windows to gain a lot more free space than I ever had previously.  It might not be the normal  routine I'll follow, but perhaps when farkling reaches such a terminal-effort level of the OS it's more time-consuming but a lot less frustrating in the end.

16

Tweaking.com Support & Help / Re: Running v4.4.1 farkles Windows Update on Win10 w/ 0x80070643 error

« on: January 28, 2019, 01:23:47 pm »

There is simply no way to expand the internal SSD or RAM on this particular model; at this point Office Depot wouldn't take it back, and Toshiba's US operation has been so decimated it's doubtful there is much opportunity for relief from that perspective.  The upgrade process insists it must have 8 Gb on the drive, and won't even offer the option to utilize additional memory on an attached (and recognized in Explorer) 64 Gb USB drive which has been formatted to NTFS.  The OS itself takes up almost 25 Gb, so there is simply no way to continue with that process -- it won't get beyond that 8 Gb-reduction demand when I run the MS 1809 Media Creation Tool, and so I seem to be in a "Catch-22" situation of the worst sort.

I really appreciate all your efforts but it seems I'm just SOL and am going to reinstall Panda Dome (so I have some sort of functional AV), then ignore the Defender updates until I can figure out how to prevent the OS from even checking for those and preclude it from failing to process other, legitimate updates its capable of handling within the limited memory.  I'll be making some acerbic comments about this situation on any MS-related forums, to be sure.

17

Tweaking.com Support & Help / Re: Running v4.4.1 farkles Windows Update on Win10 w/ 0x80070643 error

« on: January 24, 2019, 08:28:17 am »

It has not yet been offered the 1809 update, and I haven't had time to mess with trying to force it -- it's a model with memory & storage constraints which can't be modified (Toshiba didn't build those particular cl15 models with more than a 32 Gb base non-upgradeable SSD), and the whole-hog approach MS adopted with Win10 renders each major update is a true PITA to achieve successfully (often involving offload of installed apps to gain sufficient space).  Had I known it was going to be such a problem machine, I wouldn't have bought it despite its bargain price and being a handy tool for portable use.  I don't remember what the original build was, but the laptop is 3 years old so in the 15xx series, I think.

The last time it got farkled in a major Windows update I had to go back to the original image from a USB stick from Toshiba and rebuild from that -- not particularly looking forward to re-doing that process (but may have to), so when I get time over the next few days I'll try the repair install approach.

18

Tweaking.com Support & Help / Re: Running v4.4.1 farkles Windows Update on Win10 w/ 0x80070643 error

« on: January 23, 2019, 01:45:49 pm »

I've uninstalled Panda Dome, first from within Windows and then after rebooting by applying the Panda uninstaller.  Tried it again after rebooting, and no joy (same error message) -- since I have run Panda in parallel with all flavors of Windows on all of my machines (XP, Win7, Win10) since 2013 and began using the TwAiO tool in 2014 on them without this type of symptom in any of them prior to this latest version, there simply is not a conflict in my experience.  I had not run the TwAiO tool on the two Win10 machines for about 6 months (i.e., several version updates), and when I did so last week it was immediately after running the battery of weekly malware scans on both.  I'm certain it was the TwAiO tool which has produced the farkled situation, but what allowed one machine to become repaired with the battery of helpful commands you've provided and not the other, is just not clear and I may have to revert to the out-of-box OS and completely reconfigure it all over -- not a happy outcome.

19

Tweaking.com Support & Help / Re: Running v4.4.1 farkles Windows Update on Win10 w/ 0x80070643 error

« on: January 19, 2019, 07:07:55 am »

I appreciate the assistance, but please be aware I am not a newbie with computers (have been dealing with mainframes, minicomputers and then PCs from the early 1970s onward); I've been running the Panda Dome AV -nee FREEAV- in parallel with Defender or MSE on various Windows computers for years without this particular sort of issue -- they are not incompatible.  When I have time later today, I'll uninstall Domeand test on that particular laptop to see whether WU will then install its updates, and if so re-install Dome and retest.

20

Tweaking.com Support & Help / Re: Running v4.4.1 farkles Windows Update on Win10 w/ 0x80070643 error

« on: January 18, 2019, 12:26:32 pm »

Well, there is some progress as a result of those actions -- WU did identify both a Defender update and the 2019-01 W10v1803 update, then proceeded to download and attempt to install those two items.  The 2019-01 update was successful; the WU update failed with that same 0x80070643 error.

So, it's good that the non-Defender updates are processed successfully; Panda Dome is the primary AV on that machine and Defender was set to run periodically, and I wondered if that setting was still valid -- turns out, there's a problem with Defender which might provide insight.  That "periodic scanning" toggle had reverted to the default "Off" position, and when I toggled it to "On" then clicked "Yes" for the subsequent UAC shield, it turned "Off" -- ran back through the Powershell commands again, rebooted and tried again but the same behavior remains.

21

Tweaking.com Support & Help / Re: Running v4.4.1 farkles Windows Update on Win10 w/ 0x80070643 error

« on: January 17, 2019, 07:59:56 am »

Thanks very much for your response and advice -- I had run the dism /restorehealth earlier (but without the /startcomponentcleanup switch) on the laptop which was experiencing the endless CHKDSK, that never budged beyond 10% even though I'd let it run for several hours before I had made the initial post.  That symptom was unique to the 1809 machine, which afterward had crashed with a BSOD followed by some Dell-flavored recovery process that was wanting to reinstall a completely clean image (i.e., return to an out-of-box state) -- I chose instead to toggle the power-button icon that was offered and rebooted to a normal desktop, at which point I ran through all of those commands as you outlined in an administrator-enabled Powershell window, but specified the /X switch in the CHKDSK command to dismount the volume.  This seems to have completely resolved the WU issue it was experiencing, and all seems back to normal.

Not so for the 1803 laptop (a Toshiba with space-constrained SSD, so unlikely to experience a drive failure); although I've run the various Windows troubleshooters and had them "fix" the issue(s) found and then through the same process you outlined that worked with the 1809 laptop, that 0x80070643 error continues when WU runs.  In looking over the Event Viewer details, all but one of the most recent failure is associated with the standard KB for Windows Defender updates (KB2267602), but the latest includes an additional entry for the latest security update (KB4023057, the 2018-11 update) -- MS indicates this update is available through WU, but not independently through the update catalog.

Further thoughts?

22

Tweaking.com Support & Help / Re: Running v4.4.1 farkles Windows Update on Win10 w/ 0x80070643 error

« on: January 13, 2019, 07:22:43 pm »

There were exactly two registry backups from yesterday (and none earlier), so I toggled the first and had the program restore it, then rebooted and tried WU -- no joy with the 1st candidate, same error citation.  The 2nd candidate has gone into a chkdsk-at-boot cycle that seems to have reached a plateau at 10% complete.

There was no system restore point in the 1st candidate to select, despite the fact I had the app create one before launching it for its automated run and shutdown.  I haven't yet been able to check that feature in the 2nd candidate because of the stalled disk check.

23

Tweaking.com Support & Help / Re: Running v4.4.1 farkles Windows Update on Win10 w/ 0x80070643 error

« on: January 13, 2019, 02:44:21 pm »

Unfortunately, although I made certain to establish backup and restore points within TwIA1 before kicking it off on each machine, neither one now recognizes that it did that and finds no previous restore point at all.

24

Tweaking.com Support & Help / Running v4.4.1 farkles Windows Update on Win10 w/ 0x80070643 error

« on: January 13, 2019, 01:50:50 pm »

I have 2 Win10 Home laptops on which I yesterday ran overnight the latest version of the all-in-one repair tool (something I do 2-3 times/year) after their regularly weekly battery of malware scans, and today cannot successfully update the OS to install the latest Windows Defender definitions -- it now consistently fails with that 80070643 error message, implicating the TwAI1 app.  I've followed a number of the MS-provided suggestions (namely opening a Powershell window with administrative privileges and running the SFC, DISM and CHKDSK tools within before rebooting) without regaining full function, searched for non-MS advice without finding any magic bullets and so thought I'd post a problem description here to see if there were other sage bits of advice which might be offered by the app cognoscenti.

Both laptops had no problems with the round of Patch Tuesday updates last week, have generally been kept up-to-date in all other respects, and both have the 64-bit OS flavor (one is build 1803, the other 1809).  My first inclination is to go back to the restore point I'd set before launching TwAI1 and see if that resolves the issue, but want to start a thread and then provide updates as I try that on each machine.