Power BI Desktop - PBIX file not locked when open

[mike_honey]

Power BI Desktop no longer appears to lock PBIX files when they are open.  I'm sure this used to be the case up to a few months ago.

Steps to reproduce:

1. Using Windows Explorer, navigate to your PBIX file

2. Double-click the file to open it in Power BI Desktop

3. Return to Windows Explorer

4. Double-click the same file to open it in Power BI Desktop .. again !?!

5. Chaos

Expected result (and the way it worked previously) is that at step 4 you would receive an error that the file was already open.

Some teams use Windows File Shares to share PBIX files amongst authors - they are severely impacted by this change as you can no longer be sure if someone else has a PBIX file open.

The file does appear to be partially locked - you can't rename it once one Power BI Desktop session has it open.

[v-qiuyu-msft]

Hi @mike_honey,

I have reported this issue internally: CRI 71628939. Will update here once I get any information. 

Best Regards,
Qiuyun Yu

[v-qiuyu-msft]

Hi @mike_honey,

PG team create a defect to track this issue. No ETA on when this will be resolved. 

Best Regards,
Qiuyun Yu 

[mike_honey]

According to my testing, this issue still exists in the latest update: 

2.60.5169.3201 64-bit (July 2018)

Disappointing.

[mike_honey]

A kind-of workaround:

1. Immediately after opening a PBIX, make some trivial change and hit save
2. If you are the winner, the file will save - you can smile smugly and continue working
3. If you are a loser, you will receive an error about the file being open in another process (the error that should appear when you tried to open the file). Use your thumb and forefinger to make the shape of a letter L, and apply it to your forehead. 

[mike_honey]

According to my testing, this issue still exists in the latest update: 

2.61.5192.541 64-bit (August 2018)

More disappointment.

[mike_honey]

According to my testing, this issue still exists in the latest update: 

2.63.3272.40461 64-bit (October 2018)

[mike_honey]

According to my testing, this issue still exists in the latest update: 

2.64.5285.582 64-bit (November 2018)

@v-qiuyu-msft @Vicky_Song

[mike_honey]

According to my testing, this issue still exists in the latest update: 

2.73.5586.561 64-bit (September 2019)

Over a year since it was "Accepted", would seem trivial to restore the usual and expected user behaviour?

@v-qiuyu-msft  @Vicky_Song