Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
I have a new desktop computer that I use for remote work. I am supposed to connect to a computer in my office via Windows Remote Desktop Connection. Friday was the first day I had this computer, and the remote connection was not yet set up. So I set up a practice project on the computer without the connection.
But today, the remote connection is up and running, so I booted it up. Then I went to open up PowerBI. It did open up just fine. But the moment I clicked out of PowerBI to find the dataset I would be using, the software froze up. Luckily I was able to force close it using the task manager. Then I opened PowerBI again and went to find the dataset again, and it froze up again!
I need the software to work within the remote connection so I can use it for my job.
May I ask which verson you are running? I had that issue with some of the former versions as well. It was fixed end of March I think.
Currently running on June 2022 version I have no problems like that anymore.
Cheer
Daniel
OK 😞
Have you tried deactivating the preview feature "Power I Desktop infrastructure update"?
Daniel
Daniel,
Please read below for my response to Jing. It seems my problem fixed itself.
Hi @Anonymous
If you want to work on Power BI Desktop within the remote connection, you need to install Power BI Desktop on the remote computer. Has this been done?
"But the moment I clicked out of PowerBI to find the dataset I would be using, the software froze up. " What do you mean by the "dataset"? Do you want to open an existing report (pbix file) in the remote computer? Is this file on the remote computer or on the current new desktop computer?
Best Regards,
Community Support Team _ Jing
Jing,
Here's what I did, in the order I did it:
Then after I force closed PowerBI using Task Manager, I did the following:
Now, here's what happened today when I tried to recreate the problem:
Thanks for your response. If you have any thoughts on why the computer might have been acting up, I would be interested to hear them. But it looks like my issue resolved itself and all I needed to do was wait.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
88 | |
86 | |
83 | |
65 | |
49 |
User | Count |
---|---|
127 | |
108 | |
88 | |
70 | |
66 |