Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - davenz

Pages: [1]
1
Hi Julian

I only have the usual Windows Defender running and disabling this makes no difference. I have no other TSR-monitoring type programs running. The tool 'knows' there is an upgrade, when I click the Check for Updates button, so that part of it is working, it just tanks with that error when I click the Download Update button as per the image.

2
Hi team, not a complaint, more a report for whatever it is worth. I upgraded to version 4.0 pro, then when I restarted the software I received an update notification to version 4.0.1 and when I opened the update tool (well, it opened for me) and I hit the download button, I received an unknown error message in the dialogue box and the download failed due to downloader error. I tried restarting the software and manually invoking the update tool but it's the same, so I am downloading a new setup file as I write this. It might be because everyone is hitting the update server, but I thought I'd report it anyway.

Cheers,

Dave.

3
Tweaking.com Support & Help / Re: Initialisation error
« on: May 06, 2017, 05:51:10 pm »
No AV software other than Windows Defender; I should have added I disabled it when installing Windows Repair once I started having issues but that made no difference to the result. I have nothing else running that could interfere with the install. Like I said, all other updates I do using the built-in update feature worked fine until this version, when it appeared to update properly but wouldn't run without throwing up that error. That's when I uninstalled it (using Geek Uninstaller) and reinstalled several times trying different strategies each time; it still chucks up this error. I'll try uninstalling it and installing an older build and see how that flies and report back.

Thanks, Dave.

4
Tweaking.com Support & Help / Initialisation error
« on: May 05, 2017, 09:50:16 pm »
Hi gang.

Just downloaded the latest update (first using the pro update feature, then by uninstalling and reinstalling) and when I try to run the software all I get is an initialisation error in win-repair.exe as per the attachment. Any known issues with the latest build or is my Windows 10 pro 32-bit b0rked? I usually have the memory optimiser part of it running in the tray no problems but even that won't start now unless I manually fire it up. I can't open the main gui at all. The program has run flawlessly with no problems since I first installed and purchased it so I'm not sure what's going on with it now.

Cheers, Dave.

5
@Boggin, thanks for the information, it is much appreciated. I should also have added that this machine would also not repair install due to an error that was apparently related to different input languages or regional data between the disk/ISO I was using for repairs and the original image put on the machine at HP. No matter what resolve I tried it would not repair install (the option to choose what to keep was preset to 'None' and no other option was available) and I certainly wanted to keep the data. It got to the point I'd spent to many hours on this thing and it fought me every step of the way and so an archive/install was the only feasible repair option left.

If there is a next time I hit the SFC wall I'll try that other fix you suggested (SFC never has worked for me in 17 years of fixing computers to be honest, which is why I almost never use it - I only tried it recently due to the suggestion to pre-scan before repairs in Windows Repair (and in those times it has not fixed anything either) so it has limited value for me as a repair tool.

Thanks again for the info and all the best.

6
Hi team. I have used the pro version of Windows Repair and had a good success rate with it over the past 6 months since purchasing a license. However, the other day I had a machine in that defied all attempts at repair and I ended up archiving, formatting and reinstalling.

The history of the machine is it is a 2-year old machine running a 64-bit version of Windows 10 home upgraded from Windows 8.1 during the great giveaway. After a failed update (according to the client) the box booted but the start menu and pop-ups invoked by clicking on the volume control, network icon or other Windows-based tray apps would not show. MS Office was also buggered, with an error dialogue showing when clicking the Word (2013) or Excel shortcuts in the taskbar that a dll was missing, corrupted or not designed to run on this version of Windows. The dlls files in question (two) were present but were 0 bytes, so obviously due to be overwritten by the update (perhaps) but not replaced for whatever reason. Replacing these dlls from a known-good machine (mine) running the same version of Windows and Office threw up the same errors.

I tried the four 'usual' repairs for Windows 8/10 start menu breaking but none worked (the DISM fix and the Get app fix run in PowerShell, creating a new user profile and resetting certain registry key permissions). As a last resort I ran Windows Repair, including a SFC and pre-scan variables scans  (which found errors and repaired them) except in the case of SFC it found errors in the files but was unable to replace them, which turns out to be a common symptom that many others had with Windows 10 start menu problems.

I thought I'd report this here as like I said, I've had good results in the past with start menu errors running Windows Repair but this time, after two repair runs (I tried another one after some other changes to the OS) I had no luck. Hence I'm very happy with the software and it is a very useful tool for me and worth five times the cost. It just didn't help in this case.

Cheers,

Dave

Pages: [1]