jv16 PowerTools 2016 - Beta 5 released!

joshmcc

After installing beta 5 i ran the registry cleaner using the default safe setting and correct the found errors then rebooted, everything was fine. I ran the registry cleaner a couple more time using the other modes just to see what the results would be. I think i subsequently installed an update of skype because i remember seen hundreds of skype registry errors detected by jv16 when i ran it again. On 18 may i ran jv16 registry cleaner on the default safe mode and it came up with about 4700 errors. At the bottom of the screen there were some error messages that I do not remember. I was a little dubious with that result because i'd already cleaned the registry at the default level and the initial scan had a few hundred errors that I'd repaired. Most of the errors were under the invalid extensions section and i remember seeing things to do with cortana. It seemed that any registry entry that had a period in the value was listed. I let JV16 repair them which took many hours, then rebooted the computer. After reboot, I clicked on the start menu and received a popup windows error "critical error" to do with the start menu and it told me to log off and relog on while windows tried to fix the problem. I had no other option but to click on the ok button and let it log off. when i logged back on i got the same error regardless of weather i clicked on the start menu or the cortana search box. I didn't wait to see what other issues there were. I used JV16 restore function to restore the registry values and rebooted. Yet, I still got the same error - my system was unusable so I used system restore, after which everything was ok. I did another registry scan with jv16 on the default save level which only came up with 60 or so registry error rather than the 4700 errors previously. I also noticed that their were no error messages in the output area at the bottom of the screen as there had been previously.

Hope this is of help

Regards

Joshua

joshmcc

Further to my previous post - I ran jv16 reg cleaner at the medium level and received the errors at the bottom of the screen that I'd previously mentioned. I've attached an image file. Perhaps I made an error in my previous post. the 4700 errors may have been using the max reg scan level .. ..

regards

Joshua

jmagnuso53

jmagnuso53 wrote
I have been trying to uninstall leftover traces (see software checked in attachment). I have tried individual uninstall, group uninstall and forced uninstall with reboot with no success. Software still shows in leftover traces. One worrisome trace is Quicktime, which you advertise as being able to uninstall better than others.

Followup: I was concerned about the inability to uninstall the various leftover traces showing with this beta so I installed the current version of PwrTlsX and noticed these leftover traces were not listed. Either your new scan is more aggressive or it is reporting false positives somehow, which I doubt. To be safe, I am going to reset Windows 10 and run Beta5 again to compare.

I have performed a Windows 10 reset, re-installed beta5 and scanned for installed programs. I again checked for leftover traces and again found several which were not installed by me, some of which have known issues. (see attached list) I am very concerned that these traces may be somehow attached to the beta 5 installation file. Can anyone else verify seeing these traces while scanning? I am again going to reset Windows and avoid installing beta 5 until this gets solved.

Update: I installed beta 5 on another computer and these several leftover traces appear as well. The common denominator is the beta installation file. I have concerns about the integrity of your systems.

leonardo

jmagnuso53 wrote
.......I have performed a Windows 10 reset, re-installed beta5 and scanned for installed programs. I again checked for leftover traces and again found several which were not installed by me, some of which have known issues. (see attached list) I am very concerned that these traces may be somehow attached to the beta 5 installation file. Can anyone else verify seeing these traces while scanning? I am again going to reset Windows and avoid installing beta 5 until this gets solved.

Update: I installed beta 5 on another computer and these several leftover traces appear as well. The common denominator is the beta installation file. I have concerns about the integrity of your systems.

Confirmed on W7-x64

csgalloway

b5 does not seem to be restarting the computer when it says it wants to. I wait a while then have to restart the computer manually.

jmagnuso53

Several days ago I posted my suspicions that the Beta5 install package was installing several software traces (after a clean install of Windows10) that have been associated with malware. Another user seems to have confirmed this as well. I am surprised that Macecraft has no comment or explanation as to why these traces are being installed. I have performed clean installs on all of the computers to eliminate these traces (could not remove using your uninstall) on my network and will not continue testing the software as I now have concerns about the integrity of your systems. I hope I am over reacting and an explanation will be forthcoming.

siliconman01

This applies to Windows 10 x64 Insider Build 14352 with CyberLink PowerDVD 16 (Licensed version).

Jv16 Beta 5 detects 4 registry keys related to PowerDVD 16 that, if removed, will completely kill PowerDVD 16. It will not even open. It has to be totally uninstalled and re-installed. Restoring the deleted registry keys will not fix the issue. A computer PowerDVD re-install is required.

pirateking42

Windows 7, jv16 PowerTools 2016 Beta Release 5.

The tags functionality is not working. I've enabled it, restarted JV16, and double-clicked an entry in the tags column and absolutely nothing is happening except for that entries' details appearing in the summary at the top (Startup Manager).

It's also broken in JV16 Power Tools X 4.0.0.157.

csgalloway

While running jvpt 2016 under Win 7 home:

: Internal Error: SafetyNet-CRKBR-1B "hkey_local_machine\Software\Classes\IRService.MediaOutputDevice\", Code: 141, Source: SS

: Internal Error: SafetyNet-CRKBR-1B "hkey_classes_root\IRService.MediaOutputDevice\", Code: 141, Source: SS

: Internal Error: SafetyNet-CREBR-2B "hkey_local_machine\software\classes\irservice.mediaoutputdevice\", "@", Code: 141, Source: SS

: Internal Error: SafetyNet-CREBR-2B "hkey_classes_root\irservice.mediaoutputdevice\", "@", Code: 141, Source: SS

Immediate help requested please....

thedude20165

Silly question, but will there be any additional updates for this Beta 5? Just wondering.

jv16

jv16 PowerTools 2017 RC1 has been released. Please see: https://www.macecraft.com/forum/viewtopic.php?f=10&t=5817

« Previous Page