Main Forum > Tweaking.com Support & Help

Install problem resolution

(1/3) > >>

jhvance:
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.

Boggin:
I've unlocked your previous thread should you wish to add to it, but in it you said that 4.4.8 installed fine in normal mode.

Have you now installed 4.5.1 ?

jhvance:
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).

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

jhvance:
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.

Navigation

[0] Message Index

[#] Next page