2. Open Notepad (Click Start, type Notepad, and then press Enter)
3. Copy and paste the following text into Notepad
Set OSBIT=32
IF exist "%ProgramFiles(x86)%" set OSBIT=64
set RUNNINGDIR=%ProgramFiles%
IF %OSBIT% == 64 set RUNNINGDIR=%ProgramFiles(x86)%
subinacl /subkeyreg "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing" /grant="nt service\trustedinstaller"=f
4. Close Notepad, and make sure you save it. When you save the text, make sure that you set Save as Type to “All Files (*.*)”. Very important! The file name needs end with .CMD. For example: fix.cmd. Lastly, when you save the file, make sure you save it at a location where it will be easy for you to find.
5. Right click on the file that you just saved in step #4, and select “Run as Adminstrator”
This is one of the things there is support for but its not free from microsoft or Dell.
I'm not going to explain it or support it. Its not a sound byte. Training and documentation for Domain Access is not simple or free. SubInACL is not an inbuilt windows tool, we need to download it .
This is one of the things there is support for but its not free from microsoft or Dell.
I'm not going to explain it or support it. Its not a sound byte. Training and documentation for Domain Access is not simple or free. SubInACL is not an inbuilt windows tool, we need to download it .
No help. Still getting the VSS Errors triggered by SDSSnapshotProcess
Now, please go that article and look at its proposed Solution 2. I am wary about it because it changes access or something at a high level, and NOT two levels down in a particular DCOM component.
What do you think about that article's Solution 2?
Dell Support -- and we paid for three years of on-site help for these three new high-end PCs -- has advised that this issue is outside their support obligations.
Even though I last emailed them that "The VSS Errors are triggered immediately – and only -- by a process called SDSSnapshotProcess, which Dell might have purchased from a third-party vendor called SoftThinks SAS. No idea what it does. But could Dell reach out to them to find a solution?"
This is still an issue. It is happening at least twice a day on three new Dell PCs - two Optiplex 7000s and one Precision 3660.
I will not be trying the above Solution 2 because it comes from a tiny tech article from a writer who has no followers. Also, I emailed him and he did not respond.
Dell Support has washed its hands and says this type of issue is not covered by them. Yet I think it is triggered by one of Dell's own added apps/services.
Based on what I found, I believe this is related to the Dell SupportAssist Remediation application because it uses VSS to take snapshots of the system. Uninstalling that application will most likely fix this issue.
@jesster Agree that DSA Remediation is part of the problem. We've removed the application but it keeps returning and systems start crashing about once every hour to hour and a half when it's back. I've removed DSA completely from 2 machines now and waiting to see if that works.
I stumbled across this thread while troubleshooting an issue for a user that has been encountering a BSOD every hour and ~8 minutes starting Tuesday morning (11/18). In looking at the dump files, it appears DSA might be causing the issue, so we will uninstall it and hope that @jesster is correct. While annoying, at least it is consistent at 1hr and 8 minutes, so the user starts to save everything at 1hr 5 minutes and waits for the inevitable crash. :)
@wilcom16 That was our hope as well. We have this happening on 10 devices so far across 6 clients, all starting within the last 7 days. Since SDSSnapshotProcess is also involved when we look at the dump file, we wondered if there was a setting in SupportAssist where we could turn off the snapshot. Have not had time to dive into it today, but something we're going to look at. Just thought I'd throw it out there if anybody knew and could save us a little time. :)
@Robb4242 yikes, we have around ~45 Dell workstations and laptops, and most have DSA on them and running routinely, hoping this is an isolated incident... I'll let you know if I find the setting to turn off the snapshot.
@Robb4242 I uninstalled Dell SupportAssist Remediation, and ran SFC (it reported it found and repaired corrupt files) and it is now 1hr and 30 mins with no issues. Fingers crossed but it's the first time in 2 days it hasn't restarted after an hour and 8 minutes.
@wilcom16 When we only removed the DSA Remediation, it worked fine for a couple of days and then started again. We found that Remediation had been reinstalled automatically.
speedstep
9 Legend
•
47K Posts
0
August 11th, 2022 08:00
@glnz
Your windows came from an enterprise where users don't have full permissions.
error 0x80070005
Either do clean install with local accounts or Admin Subacl Fix.
To correct the problem, you can try the steps below.
1. Download and install subinacl from the Microsoft
subinacl.msi
2. Open Notepad (Click Start, type Notepad, and then press Enter)
3. Copy and paste the following text into Notepad
Set OSBIT=32
IF exist "%ProgramFiles(x86)%" set OSBIT=64
set RUNNINGDIR=%ProgramFiles%
IF %OSBIT% == 64 set RUNNINGDIR=%ProgramFiles(x86)%
subinacl /subkeyreg "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing" /grant="nt service\trustedinstaller"=f
4. Close Notepad, and make sure you save it. When you save the text, make sure that you set
Save as Type to “All Files (*.*)”. Very important! The file name needs end with .CMD. For example: fix.cmd. Lastly, when you save the file, make sure you save it at a location where it will be easy for you to find.
5. Right click on the file that you just saved in step #4, and select “Run as Adminstrator”
glnz
2 Intern
•
310 Posts
0
August 11th, 2022 09:00
speedstep - thanks.
speedstep
9 Legend
•
47K Posts
0
August 11th, 2022 13:00
@glnz
The link works fine for me.
subinacl.msi
This is one of the things there is support for but its not free from microsoft or Dell.
I'm not going to explain it or support it. Its not a sound byte. Training and documentation for Domain Access is not simple or free. SubInACL is not an inbuilt windows tool, we need to download it .
subinacl WIKI
sysinternals-suite
By Mark Russinovich
Updated: July 19, 2022
https://www.microsoft.com/store/apps/9p7knl5rwt25
speedstep
9 Legend
•
47K Posts
0
August 11th, 2022 13:00
@glnz
The link works fine for me.
subinacl.msi
This is one of the things there is support for but its not free from microsoft or Dell.
I'm not going to explain it or support it. Its not a sound byte. Training and documentation for Domain Access is not simple or free. SubInACL is not an inbuilt windows tool, we need to download it .
subinacl WIKI
sysinternals-suite
By Mark Russinovich
Updated: July 19, 2022
https://www.microsoft.com/store/apps/9p7knl5rwt25
SubInACL is no longer supported in Windows
To change the permission of a folder, follow the steps below:
Press Windows key + E on the desktop screen.
Right-click on the documents folder.
Click on Security tab, then click on Edit to change the permissions.
Click the box to allow Home Users full control.
Click OK
glnz
2 Intern
•
310 Posts
0
August 15th, 2022 08:00
UPDATE FROM OP --
I have tried two things that have NOT worked for this problem:
1) I have run Macrium Reflect's "Fix VSS Problems" and rebooted.
2) I have gone to this article: https://www.yourdigitalmind.com/tutorials/how-to-fix-volume-shadow-copy-service-error-unexpected-error-querying-for-the-ivsswritercallback-interface/ and run its Solution 1 only.
No help. Still getting the VSS Errors triggered by SDSSnapshotProcess
Now, please go that article and look at its proposed Solution 2. I am wary about it because it changes access or something at a high level, and NOT two levels down in a particular DCOM component.
What do you think about that article's Solution 2?
Thanks.
glnz
2 Intern
•
310 Posts
0
August 16th, 2022 06:00
Dell Support -- and we paid for three years of on-site help for these three new high-end PCs -- has advised that this issue is outside their support obligations.
Even though I last emailed them that "The VSS Errors are triggered immediately – and only -- by a process called SDSSnapshotProcess, which Dell might have purchased from a third-party vendor called SoftThinks SAS. No idea what it does. But could Dell reach out to them to find a solution?"
My question is still whether Solution 2 in the article at https://www.yourdigitalmind.com/tutorials/how-to-fix-volume-shadow-copy-service-error-unexpected-error-querying-for-the-ivsswritercallback-interface/ is safe.
What do you think?
glnz
2 Intern
•
310 Posts
0
August 31st, 2022 10:00
This is still an issue. It is happening at least twice a day on three new Dell PCs - two Optiplex 7000s and one Precision 3660.
I will not be trying the above Solution 2 because it comes from a tiny tech article from a writer who has no followers. Also, I emailed him and he did not respond.
Dell Support has washed its hands and says this type of issue is not covered by them. Yet I think it is triggered by one of Dell's own added apps/services.
Does anyone else see this in Event Viewer?
Bell98
1 Rookie
•
22 Posts
0
June 17th, 2023 07:00
Yes
jesster
21 Posts
0
August 20th, 2024 16:19
Based on what I found, I believe this is related to the Dell SupportAssist Remediation application because it uses VSS to take snapshots of the system. Uninstalling that application will most likely fix this issue.
Robb4242
1 Rookie
•
6 Posts
0
November 20th, 2024 15:30
@jesster Agree that DSA Remediation is part of the problem. We've removed the application but it keeps returning and systems start crashing about once every hour to hour and a half when it's back. I've removed DSA completely from 2 machines now and waiting to see if that works.
wilcom16
1 Rookie
•
3 Posts
0
November 20th, 2024 19:56
I stumbled across this thread while troubleshooting an issue for a user that has been encountering a BSOD every hour and ~8 minutes starting Tuesday morning (11/18). In looking at the dump files, it appears DSA might be causing the issue, so we will uninstall it and hope that @jesster is correct. While annoying, at least it is consistent at 1hr and 8 minutes, so the user starts to save everything at 1hr 5 minutes and waits for the inevitable crash. :)
Robb4242
1 Rookie
•
6 Posts
0
November 20th, 2024 20:12
@wilcom16 That was our hope as well. We have this happening on 10 devices so far across 6 clients, all starting within the last 7 days. Since SDSSnapshotProcess is also involved when we look at the dump file, we wondered if there was a setting in SupportAssist where we could turn off the snapshot. Have not had time to dive into it today, but something we're going to look at. Just thought I'd throw it out there if anybody knew and could save us a little time. :)
Key : CriticalProcessDied.Process
Value: DellSupportAss
Key : CriticalProcessDied.Symbol
Value: SDSSnapshotProcess.dll!
Key : CriticalProcessDied.TerminatedBy
Value: DellSupportAssistRemedationService.exe
Key : CriticalProcessDied.WERReportId
Value: 16f6179d-b30c-454e-a2ab-1308ec9657de
Key : Failure.Bucket
Value: 0xEF_DellSupportAss_BUGCHECK_CRITICAL_PROCESS_TERMINATED_BY_DellSupportAssistRemedationService.exe_58336080_SDSSnapshotProcess.dll!
wilcom16
1 Rookie
•
3 Posts
0
November 20th, 2024 20:22
@Robb4242 yikes, we have around ~45 Dell workstations and laptops, and most have DSA on them and running routinely, hoping this is an isolated incident... I'll let you know if I find the setting to turn off the snapshot.
DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump FAULTING_THREAD: ffffa68893414080 PROCESS_NAME: DellSupportAss CRITICAL_PROCESS: DellSupportAss ERROR_CODE: (NTSTATUS) 0x93414080 - <Unable to get error code text> CRITICAL_PROCESS_REPORTGUID: {0bef9902-f6e1-482c-87b8-ca8434302a8c} IMAGE_NAME: SDSSnapshotProcess.dll MODULE_NAME: SDSSnapshotProcesswilcom16
1 Rookie
•
3 Posts
0
November 20th, 2024 22:07
@Robb4242 I uninstalled Dell SupportAssist Remediation, and ran SFC (it reported it found and repaired corrupt files) and it is now 1hr and 30 mins with no issues. Fingers crossed but it's the first time in 2 days it hasn't restarted after an hour and 8 minutes.
Robb4242
1 Rookie
•
6 Posts
0
November 20th, 2024 22:10
@wilcom16 When we only removed the DSA Remediation, it worked fine for a couple of days and then started again. We found that Remediation had been reinstalled automatically.