Messages

1

General Computer Support / Odd new sfc issue

« on: December 14, 2018, 05:07:26 pm »

Windows 10 Pro 64 bit
Samsung 500GB SSD

Whenever I run sfc in the Windows environment, it always says it found corrupt files and was not able to repair some of them.  DISM appears to repair the component store, but running sfc again always results in the same message.  However, if I run sfc in safe mode it finds no integrity violations.  Would sfc be more likely to produce an accurate result in safe mode?  On occasion, sfc has found issues in safe mode, but it fixed them all with one exception where I had to clean up the component store first.  Today sfc found issues, so I immediately rebooted into safe mode and ran it again...found no violations.

2

General Computer Support / Windows 10, version 1803 - Cumulative update KB 4103721 - failure to boot

« on: May 10, 2018, 06:06:03 am »

If anyone has had a black screen after attempting to install Cumulative Update KB 4103721, and has Advanced System Care 11 installed, here is the fix:

Rebooting to Safe Mode will trigger a rollback of the update, but you'll need to reboot to Safe Mode a second time to finish the rollback and perhaps a third to actually get into Safe Mode.  Once there, you can reboot into Windows.

In Services, shut down and disable Advanced SystemCare Service 11, reboot and then install the update.  Once installed you can enable and start the service again.

3

Tweaking.com Support & Help / Re: Non fixable Reparse point on Windows 10

« on: March 30, 2018, 02:40:25 pm »

jpm,

The target path that the repair is trying to create is incorrect...notice the double C reference: C:\\C:\inetpub\temp\appPools\DefaultAppPool
Clearly a syntax error in the software I would think.

4

Tweaking.com Support & Help / Non fixable Reparse point on Windows 10

« on: March 28, 2018, 09:47:10 am »

This seems fairly common, but I wanted to get some thoughts on the attached syntax error in creating the directory.

5

General Computer Support / Issue with Audacity on Windows 10 Pro 64 bit, version 1607

« on: May 07, 2017, 07:21:57 am »

Has anyone come across this one before:

Activation context generation failed for "C:\Program Files (x86)\Audacity\audacity.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.953_none_42151e83c686086b.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.953_none_89c2555adb023171.manifest.

6

General Computer Support / Automated fix for common error in Windows 10 Pro 64 bit, version 1607

« on: May 07, 2017, 07:17:59 am »

I have found this referenced on the web, but the fix is a bit too much for me to manage.  I wondered if anyone had put together a script to sort this one out:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
 and APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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.

7

General Computer Support / Re: Reparse points missing after each update

« on: January 16, 2017, 04:41:20 pm »

Too many software updates since...I will check daily until the next update, then immediately after to confirm again.

8

General Computer Support / Re: Reparse points missing after each update

« on: January 16, 2017, 04:19:38 pm »

Yes.  All but three are repaired on the first run, those require a second run.  I would like to ask others to cross check this.  Very odd...

9

General Computer Support / Reparse points missing after each update

« on: January 16, 2017, 03:53:44 pm »

I have confirmed the loss of most if not all reparse points concurrent with each and every Windies 10 update...have no idea why.

10

General Computer Support / Re: Windows 10 error

« on: November 12, 2016, 04:15:34 pm »

Thanks!  I had the CAPI error as well, but sorted that one out.

11

General Computer Support / Re: Odd Behavior

« on: November 12, 2016, 11:24:01 am »

I ended up doing a clean install of the OS, which seems to have addressed the issues I was having.  Before I got to that, I had replaced the system HDD, Power Supply and the Motherboard (albeit the same model).  So this thread can be considered closed.

12

General Computer Support / Windows 10 error

« on: November 12, 2016, 11:15:41 am »

This seems to be a common permissions error:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
 and APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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.

I have found a Power Shell script that can be customized for these particular keys, but there are some steps to change permissions back afterwards that I am unclear on.  Would running the Permissions Repairs in the tool afterwards do the trick?  The suggested script is attached.

13

General Computer Support / Re: Odd Behavior

« on: October 21, 2016, 11:46:21 am »

My issue is Explorer, not IE.  Today the screen went black...and the power button on the tower will not shut down or reboot the system...had to use the rear switch...so...Power Supply and Board time.  I have ordered both and was able to find an exact replacement for my board, so it will accept the existing Processor and Memory, and there will be no driver issues...such a pain though!

14

General Computer Support / Re: Odd Behavior

« on: October 20, 2016, 09:45:39 am »

Things are going quite well...very smooth with a few exceptions:  I am getting occasional Explorer hangs, and Event Viewer is replete with errors, but all were generated during the period that I was attempting to get the new DRAM sorted...I will check for other errors going forward.

15

General Computer Support / Re: Odd Behavior

« on: October 20, 2016, 06:38:41 am »

Boggin,  Yes, I did use the Crucial scanner to find a set.  This morning I installed one of the new sticks, and it booted.  I shut it down and then enabled XMP selecting Profile 1 for both channels.  I then manually entered the correct timings for the new sticks.  On reboot, I got the memory changed warning from the BIOS, but after saving and rebooting a few times, the settings took.  I verified both with the BIOS and HWInfo.  I then installed the other sticks in the other channel and after a few attempts now have all 16 GB running at appropriate speed and timings.  Now to see if I have further read issues...if so, would it more likely be the board or perhaps the Power Supply?  I will do another restore point and another image backup tonight just in case.

16

General Computer Support / Re: Odd Behavior

« on: October 19, 2016, 08:32:12 pm »

Thanks!  I am monitoring voltage with HWMonitor and find everything in range.  I have to figure out how to enable XMP and make some manual timing adjustments to accommodate the new memory as it would not boot and kicked up the BIOS Setup.  I pulled some info together and will have a go at it tomorrow.  Failing that, I will exchange these sticks for a set running at the current DRAM settings.  Memory errors are getting more frequent..."referenced at ______ cannot be read".  I did clear the CMOS and replace the battery.

17

General Computer Support / Odd Behavior-Solved

« on: October 18, 2016, 04:42:33 pm »

Hi All,

  I have a home built running Windows 10 Pro 1607.  It currently has 8GB of DRAM.  Recently, about once per week it will not fully boot up (it will usually get to the desktop, but not everything will load and the screen will go black, and then try again, etc.), and sometimes on shutdown or when initiating a restart, it will flash a memory could not be read message.  Since the HDD was about 5 years old, I decided to replace it.  Prior to this, using either a System Restore point or restoring from a drive image would get me back up...but only for another week or so.  It ran great after the HDD replacement...for another week, then the same symptoms returned.  I tested the DRAM with both the built in Windows tester and Memtest 64+, which I ran overnight but didn't report any errors.  I have 16 GB of Crucial DRAM arriving tomorrow, so we'll see what happens.  My thinking is that it may well be DRAM issues causing file corruption on the HDD over time, or when a certain part of the memory is accessed.  I have had an issue years ago with a bad Memory slot on the Motherboard, so I am hoping it is not that.  Anyone know of any Power Supply monitoring software that might pick up possible issues?  It is the one other possibility aside from the board itself.
  The other odd thing is when booting to Safe Mode with Networking, there is an endless attempt to open the Microsoft website in Chrome (it is my default browser), but not just one tab...endless tabs...makes it almost impossible to get anything done as the browser always steals focus.  On two occasions, Safe Mode would not fully load either when trying it after a failed normal boot.

18

General Computer Support / Re: Locked topic...Shutdown issues after Windows 10 upgrade

« on: April 07, 2016, 07:56:17 am »

Just a note to let you know that apparently on install, Windows 10 installed a more recent albeit generic SMBUS driver from Synaptics during setup.  One of my searches came up with the older Intel version for this chipset and the tower shuts down completely every time now!  I have WU set to not update any drivers, so I should not have a repeat install of the other version.   

19

General Computer Support / Re: Windows 10 Pro 64 Reparse Points

« on: February 15, 2016, 07:13:55 pm »

Update!  I was able to verify that the folders in question were in fact empty and used Unlocker to delete them.  I ran the scan again and it found the 3 missing and I ran the repair with success.  I will now run chkdsk.

20

General Computer Support / Windows 10 Pro 64 Reparse Points

« on: February 14, 2016, 03:06:07 pm »

Hi all,  I have found it very odd that I had no issues with reparse points prior to the last batch of updates...at least not since the prior batch.  Now I have three that I cannot repair as they are not empty and cannot be deleted.  Log is attached.

21

Everything Else / Interesting issue with Reparse Points after Windows 10 Threshold 2 update

« on: November 21, 2015, 12:00:38 pm »

Just a note to let you know that while there had been no issues at all on either the laptop or desktop found with the Pre-scan Tool, immediately after the Threshold 2 update there were a whole raft of them...identical on both machines...after an initial repair run, there were 3 that needed a repeat to clean up, again, identical on both machines.

22

General Computer Support / Re: Desktop migration: XP to Windows 10 - power management issues

« on: October 09, 2015, 05:39:49 am »

Hi Shane,

  I did manage through the Group Policy Editor to have it not ask for a password on waking.  I did find out that MSI is working on a new BIOS for the board to better suit Windows 10.  Apparently the issue is widespread with a whole host of causes attributed to it, none of which applies to my machine.  I am guessing the OS/BIOS combo to be the issue, but cannot be sure.  The only other odd thing is that the laptop can access the desktop files via simple file sharing quite nicely, but not the other way around.  Both Windows 10 with identical sharing settings...I'll figure it out eventually.  In the meantime, it works.  It was rather stunning to see what a 64 bit system will do with the 8 GB of RAM that have been in here for all this time...

23

General Computer Support / Re: Desktop migration: XP to Windows 10 - power management issues

« on: September 22, 2015, 04:47:00 am »

Julian,  Wired Mouse and Keyboard.  I went back to the S1 setting and can again wake the machine from the reset button, so for the moment I can live with that. I have attached a screenshot of the Command Prompt info at this setting.

24

General Computer Support / Re: Desktop migration: XP to Windows 10 - power management issues

« on: September 21, 2015, 01:12:14 pm »

Julian,  Did that, rebooted and placed into Sleep...again, Sleeps like a log but won't awaken with any inputs...and this time not even the reset button on the tower.  Had to do a hard kill...(ouch).  Think I will change it back and consider unchecking Fast Startup.  I suspect the BIOS isn't fully compatible with Windows 10, but I can live with it.  I am however compelled to find out why...lol!  At least with Fast Startup disabled and S1 in place, the Reset button brings things back up. I attached a screenshot of the Command Prompt.

25

General Computer Support / Re: Desktop migration: XP to Windows 10 - power management issues

« on: September 21, 2015, 04:54:25 am »

Julian, This BIOS can be set for either S3 or S1, and is currently set to S1.  I have also set it to wake with both the keyboard and the mouse, but to no effect.  The more research I do on this, it seems that on slightly older hardware with Legacy BIOS, Windows 10 just behaves this way.  I found some info that indicated possible solutions, but none of them apply in my case.  A new Intel Management Interface Driver has been implicated, but only on Intel boards in HP machines.  Information from Microsoft on shutdown procedures indicates using the Power button after shutting down the OS, so it may be something I have to live with having this Motherboard and BIOS.  I thought of a third Party BIOS, but it makes me a bit nervous. Having set things to display ongoing processes during start up and shutdown, I can verify that the system is shutting down...it's just that the power light and fans continue to run until I use the Power button on the tower.  Perhaps the OS won't interface with the ACPI in this older BIOS.