Reply
SanDisk Guru
Posts: 2,784
Registered: ‎07-23-2010

Re: SanDisk Secure Access V3 fails to start

If you don't want it, don't use it, and DELETE the files and folders associated with it.  Not a big deal imho.

Ed
Important files = Backed up files
Newbie
Posts: 9
Registered: ‎10-10-2018

Re: SanDisk Secure Access V3 fails to start

How it's greyed out tried everything diskpart remove write protecting .......

SanDisk Guru
Posts: 2,784
Registered: ‎07-23-2010

Re: SanDisk Secure Access V3 fails to start

hmmm Open a Command Prompt window and run a ATTRIB command for the USB drive.  Post the results please. 

Ed
Important files = Backed up files
SanDisk Guru
Posts: 2,784
Registered: ‎07-23-2010

Re: SanDisk Secure Access V3 fails to start

attrib  ?:\*   /d

 

Replace the ? with the drive letter of your SanDisk drive.

Ed
Important files = Backed up files
Newbie
Posts: 9
Registered: ‎10-10-2018

Re: SanDisk Secure Access V3 fails to start

Hi Ed

 

Please see attached

 

Cheers Sean

 

CMD.JPG
SanDisk Guru
Posts: 2,784
Registered: ‎07-23-2010

Re: SanDisk Secure Access V3 fails to start

Is your USB drive plugged in?  And if it is what drive letter has Windows assigned to it?

 

Do note there is suppose to be a blank space between the * and the /.

Ed
Important files = Backed up files
Newbie
Posts: 9
Registered: ‎10-10-2018

Re: SanDisk Secure Access V3 fails to start

Yes of course its plugged in and showing as D Smiley Mad

Amazed this write protection cannot be wiped.

Still showng Parameter format not correct

 

Cheers Sean

 

 

CMD2.JPG
SanDisk Guru
Posts: 2,784
Registered: ‎07-23-2010

Re: SanDisk Secure Access V3 fails to start

attrib d:\*  /d

 

Only 2 spaces, one after attrib and one after *.

Ed
Important files = Backed up files
Newbie
Posts: 9
Registered: ‎10-10-2018

Re: SanDisk Secure Access V3 fails to start

Got it Cheers 

 

 

CMD3.JPG
SanDisk Guru
Posts: 2,784
Registered: ‎07-23-2010

Re: SanDisk Secure Access V3 fails to start

[ Edited ]

Excellent.  Also excellent quality screen image.

 

Now there is one SecureAccess file that is Hidden which prevents it from being seen and deleted.  It may be contributing to your SecureAccess problem.  So let's unHide it.

 

There is 1 space after attrib and 1 space after the h.

 

attrib  -h  d:\*.tmp

 

After running try deleting the file.

 

del d:\*.tmp

 

Then do another  attrib d:\*  to verify it's gone.  Then try using SecureAccess.

Ed
Important files = Backed up files