Messages

1

Tweaking.com Support & Help / Aero & Sidebar fixes for Vista

« on: February 18, 2019, 02:35:12 pm »

Shane or anyone with the correct answers,

Which Windows Repairs should I run to fix Aero issues on Vista x32 SP2?

Same question, but for the Sidebar? (Notification says that DEP keeps closing and restarting Sidebar.)

Thanks in advance,
Don

2

Tweaking.com Support & Help / Re: Windows Repair Pro on Vista x86 SP2

« on: February 17, 2019, 11:48:02 pm »

Also, I need to fix sidebar/gadgets, because sidebar crashes and restarts so frequently. Do I only choose that repair or should I do others that relate to sidebar somehow?  Which repair could fix Aero issues?

Thanks again.

3

Tweaking.com Support & Help / Re: Windows Repair Pro on Vista x86 SP2

« on: February 17, 2019, 06:07:10 pm »

I thought that the program would recognize my OS, and only offer repairs for it, no?  Are they fixes that also work for Vista, even though they only say Win 8/10?

Separate question about System Tweaks (Performance).  Would you recommend enabling all of them or do you have any advice on which ones I should be careful enabling?  How would I reset them back to Windows default if I needed to?(Not saying I would ever, but jic)

Thanks so much for the help.

4

Tweaking.com Support & Help / Re: Windows Repair Pro on Vista x86 SP2

« on: February 14, 2019, 03:54:54 pm »

So is this a bug, that it is offering me Win 8/10 repairs?
I definitely need to fix Sidebar.  DEP keeps closing and restarting the sidebar.

Here is a screenshot.

5

Tweaking.com Support & Help / Windows Repair Pro on Vista x86 SP2

« on: February 14, 2019, 10:29:17 am »

When I open all repairs, I see that it shows that I'm using the Vista OS on the top of the repairs window.
My question is, I see lower down that window there are repairs selected(checked off) for Win 7 and Win 8, should I leave those selected, or unselect all the repairs that show a different OS then Vista?

Thanks in advance,
Don

6

Tweaking.com Support & Help / Re: Problem with Registry Backup v3.2.3

« on: October 06, 2015, 08:49:39 pm »

I'm glad I'm not the only one.  Same issue here, Win 10 x64.  I tried downloading portable from other servers, but they have the same issue.

7

Tweaking.com Support & Help / Re: Registry Compressor, BSOD/Possible corruption after using

« on: May 14, 2013, 04:07:29 pm »

I have a Crucial M4 256GB with newest firmware 070H.  There have been about 7 firmware updates since the drive was released.  The crash was probably SSD related, but it was short after Compressing so I was curious.  There are many people on their forums complaining about the same issue.  The drive can just "drop out" or disappear while using, which can cause Windows to BSOD and when you reboot, the "No Boot Device Found" message is displayed.  You have to "Power Cycle" the SSD for the disk to be "seen" by BIOS again.  http://forum.crucial.com/t5/Solid-State-Drives-SSD-Knowledge/Why-did-my-SSD-quot-disappear-quot-from-my-system/ta-p/65215

8

Tweaking.com Support & Help / Re: Registry Compressor, BSOD/Possible corruption after using

« on: May 14, 2013, 03:23:19 pm »

I have not run chkdsk /r in Win8 on this SSD yet.  I have on a prior SSD and in the end I RMA'd the disk, so I didn't want to unintentionally make things worse for this disk.  Do you recommend me to run chkdsk /r on my SSD now?

9

Tweaking.com Support & Help / Registry Compressor, BSOD/Possible corruption after using

« on: May 13, 2013, 09:50:33 pm »

I compressed my Win8 x64 registry with your Registry Compressor, but shortly after(1 hour) the reboot my laptop BSOD'd(Critical_Process_Died).  After booting from the BSOD, Win8 notified me that my Crucial M4 filesystem needed to be repaired.  So I rebooted so Win8 could scan and repair the SSD.  After the repair I found missing icons(ironically from another Tweaking.com program I haven't used yet), errors in event viewer and I don't know what else yet.  The disk had no issues before compressing but now I see retired blocks in the event viewer.  Is the damage already done?  Should I restore .old hives?
I already ran sfc\scannow; found no problems.