# Windows Autopsy GUI Problem!

**URL:** <https://sleuthkit.discourse.group/t/windows-autopsy-gui-problem/3697>\
**Category:** Autopsy Help\
**Created:** [April 12, 2023, 3:24pm UTC](https://sleuthkit.discourse.group/t/windows-autopsy-gui-problem/3697 "2023-04-12T15:24:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jood97](https://yyz2.discourse-cdn.com/free1/user_avatar/sleuthkit.discourse.group/jood97/32/1809_2.png) [@Jood97](https://sleuthkit.discourse.group/u/Jood97)\
**Post date:** [April 12, 2023, 3:24pm UTC](https://sleuthkit.discourse.group/t/windows-autopsy-gui-problem/3697/1 "2023-04-12T15:24:24Z")

</div>

I have a problem with the GUI of the Autopsy  
Where it becomes like this in the following Screenshots shortly after launching it  
**Knowing that the specifications of my computer I working on are high**

- GPU: RTX 3070
- RAM: 32G
- CPU: Intel i7-10700K

**Autopsy 4.19 & 4.20 same problem**

**Screenshots**

 ![1](https://global.discourse-cdn.com/free1/uploads/sleuthkit/original/2X/0/0b80150bf5eb5148fd5752a0180a34ffb4b8524a.png)  
 ![2](https://global.discourse-cdn.com/free1/uploads/sleuthkit/original/2X/2/243694fca5e19966921e13107f046341496c847d.jpeg)  
 ![Untitled](https://global.discourse-cdn.com/free1/uploads/sleuthkit/original/2X/f/fc55dfc7aeefeae1492e1dc4f7d37e1efe7bc4b5.png)

**Video**

> **[VEED - Issue.mp4](https://www.veed.io/view/c643919d-0425-40a0-929c-6a1f1c1d366a?sharingWidget=true&panel=share)**
>
> Make stunning videos with a single click. Cut, trim, crop, add subtitles and more. Online, no account needed. Try it now, free. VEED

---

<div class="post-metadata">

**Author:** ![Miovox](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@Miovox](https://sleuthkit.discourse.group/u/Miovox)\
**Post date:** [April 19, 2023, 1:13am UTC](https://sleuthkit.discourse.group/t/windows-autopsy-gui-problem/3697/2 "2023-04-19T01:13:17Z")

</div>

Same issue here.  
gpu rtx 4090  
cpu amd ryzen  
ram 128gb

---

<div class="post-metadata">

**Author:** ![Mark\_McKinnon](https://yyz2.discourse-cdn.com/free1/user_avatar/sleuthkit.discourse.group/mark_mckinnon/32/42_2.png) [@Mark\_McKinnon](https://sleuthkit.discourse.group/u/Mark_McKinnon)\
**Post date:** [April 19, 2023, 7:24pm UTC](https://sleuthkit.discourse.group/t/windows-autopsy-gui-problem/3697/3 "2023-04-19T19:24:25Z")

</div>

I can’t seem to reproduce what you and @Jood97 are seeing. The only thing that I can see that is the same for both of you is the GPU is an RTX model. Is it possible to try this on another machine or in a VM to see if you get the same issue?

---

<div class="post-metadata">

**Author:** ![Alexam](https://avatars.discourse-cdn.com/v4/letter/a/53a042/32.png) [@Alexam](https://sleuthkit.discourse.group/u/Alexam)\
**Post date:** [April 20, 2023, 5:37am UTC](https://sleuthkit.discourse.group/t/windows-autopsy-gui-problem/3697/4 "2023-04-20T05:37:45Z")

</div>

There is a thread a bit further down where more people(including me) are having the same issue. In that thread there is a person with an AMD card, so this is not only happening to people with RTX cards.

---

<div class="post-metadata">

**Author:** ![Miovox](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@Miovox](https://sleuthkit.discourse.group/u/Miovox)\
**Post date:** [May 31, 2023, 8:34pm UTC](https://sleuthkit.discourse.group/t/windows-autopsy-gui-problem/3697/5 "2023-05-31T20:34:18Z")

</div>

still no fix? its really annoying

---

<div class="post-metadata">

**Author:** ![Jood97](https://yyz2.discourse-cdn.com/free1/user_avatar/sleuthkit.discourse.group/jood97/32/1809_2.png) [@Jood97](https://sleuthkit.discourse.group/u/Jood97)\
**Post date:** [June 17, 2023, 11:19am UTC](https://sleuthkit.discourse.group/t/windows-autopsy-gui-problem/3697/6 "2023-06-17T11:19:10Z")

</div>

Hello all,  
I have found a **temporary solution** to fix it.  
I just changed the **Desktop Resolution** and returned it as it was. Takes only 20 seconds of your time!  
If this problem returns, repeat the same solution.  
**If this fix worked for you, please reply here.**
