Corrupted cache files created on Win 10 64bit, resulting with "Can't start server" permanent state

Current behavior:

When running test spec, after few initial successful launches, Cypress got stuck in a state that does not allow to run the test spec. Upon trying to launch a suite “Opening Chrome” status is displayed and after several seconds the following error message is displayed:

I’ve turned debugging on using

set DEBUG=cypress:*

but logs don’t provide any more data:

cypress:server:events send error: { 
  Error: EPERM: operation not permitted, lstat 'C:\Users\amg016\AppData\Roaming\Cypress\cy\production\browsers\chrome\interactive\CypressCache\Default\Cache\data_0'   
  cause: { 
    Error: EPERM: operation not permitted, lstat 'C:\Users\amg016\AppData\Roaming\Cypress\cy\production\browsers\chrome\interactive\CypressCache\Default\Cache\data_0'   
  errno: -4048, 
  code: 'EPERM', 
  syscall: 'lstat', 
  path: 'C:\\Users\\amg016\\AppData\\Roaming\\Cypress\\cy\\production\\browsers\\chrome\\interactive\\CypressCache\\Default\\Cache\\data_0' }, 
  isOperational: true, 
  errno: -4048, 
  code: 'EPERM', 
  syscall: 'lstat', 
  path: 'C:\\Users\\amg016\\AppData\\Roaming\\Cypress\\cy\\production\\browsers\\chrome\\interactive\\CypressCache\\Default\\Cache\\data_0' } +2ms`

Trying to manually delete the cache file referred fails - Windows provides strange message **Access is denied**, even thought I'm logged in account with local admin privileges. Further digging shows up that indeed the file is strange, as Windows doesn't provide **Owner** attribute of the file at all!
![image](https://user-images.githubusercontent.com/44611955/57697462-8eb37700-7653-11e9-8ab0-c8db116d424b.png)

(didn't know that it's possible to create a file without an owner on NTFS ???).

After digging on M$ pages I've found out that such behavior (messages like **Access Denied** even though I'm an admin) is a result of corrupted file - in order to delete the file, first chkdsk  operation has to be scheduled for the next boot up:
`chkdsk /r` 
the computer then has to be restarted, disk checking operation completed, and then I was able to manually remove the file. After removal of the file, Cypress allowed me to run the spec several times (like 5), then got stuck again.

### Desired behavior:

Cypress shall allow for arbitrary number of subsequent runs of a test spec.

### Steps to reproduce: (app code and test code)

As Current behaviour. I don't think this is related to specific test spec - it is a plain test consiting of opening a page, providing credentials, clicking of submit button, and checking if login was successful.

### Versions
Cypress:
`$ cypress --version
Cypress package version: 3.2.0
Cypress binary version: 3.2.0`

OS = Win 10 64bit

Browser = Chrome Version 74.0.3729.131 (Official Build) (64-bit)

[kandres2341]

I had this issue as well and after a good amount of trouble shooting, I found I could first restart my PC, delete %APPDATA%\Cypress, then start Cypress and it seems to fix the issue.

[jennifer-shehane]

Closing as resolved.

If you’re experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix.