voidImageViewer

[donotbugme]

to therube
silent install, software deployment..
*.msi will be even better

[moderate]

For arm32OS (Windows RT 8-1 arm32) the installer is problematic since:
An installer itself has to be arm32 PE,
+ all EXE, DLL, CAB, CAT, MSI, SYS files have to be signed with the test certificate, what developers usually don't do.

You will get the exact same result, if you will just import REG file with all installation settings.

[void]

ARM and ARM64 will be hard to do for VIV because it uses NSIS to build the installer.
NSIS doesn't support ARM/ARM64.

I have put on my TODO list to add an msi installer.

Everything has its own installer and will have an ARM/ARM64 installer soon.

Thank you for the suggestions.

[fengwhen]

Could you add these three features?

1. Drag the window by holding the left mouse button and dragging the image.

2. When an image file is opened, automatically resize the window to match the image’s dimensions so there’s no extra blank space on either side of the icon. To prevent abnormally large or small windows when an image is extremely large or small, impose both a maximum and a minimum window size.

3. Multi-language support.

[void]

1. Drag the window by holding the left mouse button and dragging the image.

I will add a left click action: Move Window.

2. When an image file is opened, automatically resize the window to match the image’s dimensions so there’s no extra blank space on either side of the icon. To prevent abnormally large or small windows when an image is extremely large or small, impose both a maximum and a minimum window size.

I will add an option to auto resize the window to show the full image (50%/100%/200%) when a new image is shown.

3. Multi-language support.

Localization is on my TODO list.

Thank you for the good suggestions.

[void]

voidImageViewer-1.0.0.13.x64.en-US-Setup.exe (266 KB)
voidImageViewer-1.0.0.13.x86.en-US-Setup.exe (251 KB)
voidImageViewer-1.0.0.13.x64.en-US.zip (184 KB)
voidImageViewer-1.0.0.13.x86.en-US.zip (164 KB)
voidImageViewer-1.0.0.13.ARM64.en-US.zip (169 KB)
voidImageViewer-1.0.0.13.ARM.en-US.zip (177 KB)
voidImageViewer-1.0.0.13.sha256 (1 KB)
voidImageViewer-1.0.0.13.src.zip (4259 KB)
https://github.com/voidtools/voidImageViewer/

Sunday, 10 August 2025: Version 1.0.0.13

• fixed an issue with losing the image center on resize
• fixed back/forward mouse buttons not working from toolbars
• fixed an issue with loading the wrong next image when it was preloaded and changed externally
• improved rendering performance
• added left click action: move window
• added auto size window GUI option

[fengwhen]

Thank you for creating such a great image viewer. After downloading and using the latest version, I’ve noticed a few small issues:

1. When an image is small (e.g., 500 × 500 px), the window automatically resizes to match the image, leaving no empty background on either side—perfect. However, when the image is very large (e.g., 4000 × 3000 px), empty background areas still appear on the left and right.

2. In full-screen mode, tiny images (e.g., 70 × 70 px) are scaled up to fit the screen, becoming so large that they turn into an unrecognizable mosaic.
Suggestion: allow users to set a maximum zoom limit, for example 500 %.

3. Some photos appear in the wrong orientation. They show as portrait in Windows Explorer thumbnails, Windows Photo Viewer, and other viewers, but appear as landscape in voidImageViewer. (I’ve heard images can store orientation metadata for lossless rotation—maybe this is related?)

4. When the left mouse button is assigned to “move window,” scrolling becomes impossible.
Suggestion: in “move window” mode, if the image is zoomed and the window can’t display it entirely, automatically switch the left button to scroll. Revert to “move window” when advancing to the next image.

5. When the window is maximized, double-clicking the image enters full-screen; double-clicking again does not simply exit to the maximized window. Instead, it goes full-screen → normal size → maximized. I’m on Windows 11 22H2 build 22621.105; I’m not sure if this is a system quirk. Could you try to reproduce it?

Once again, thank you for your work—this software is fantastic and I truly enjoy using it.

[void]

Thank you for your feedback.

1. When an image is small (e.g., 500 × 500 px), the window automatically resizes to match the image, leaving no empty background on either side—perfect. However, when the image is very large (e.g., 4000 × 3000 px), empty background areas still appear on the left and right.

I've run into this too.
The ideal solution would be to maintain the correct image aspect ratio for the clipped window size.
(So no white background areas are shown)
I'll put this on my TODO list.

2. In full-screen mode, tiny images (e.g., 70 × 70 px) are scaled up to fit the screen, becoming so large that they turn into an unrecognizable mosaic.
Suggestion: allow users to set a maximum zoom limit, for example 500 %.

This was the intended behavior when Fill Window is enabled and VIV is fullscreen. (the default setting)
Fullscreen -> Right click -> Uncheck Fill Window.
I will consider adjusting the scaling levels when Fill Window is enabled and VIV is fullscreen.

I will also trial reseting the zoom when going fullscreen (if the zoom changes drastically).

3. Some photos appear in the wrong orientation. They show as portrait in Windows Explorer thumbnails, Windows Photo Viewer, and other viewers, but appear as landscape in voidImageViewer. (I’ve heard images can store orientation metadata for lossless rotation—maybe this is related?)

I've put this on my things to fix list.
Please upload a sample photo in a bug report. It will help me fix the issue.

4. When the left mouse button is assigned to “move window,” scrolling becomes impossible.
Suggestion: in “move window” mode, if the image is zoomed and the window can’t display it entirely, automatically switch the left button to scroll. Revert to “move window” when advancing to the next image.

I thought about doing this too.
I will trial scrolling if zoomed, then fallback to move window.
-Maybe this should just be a hidden option.

5. When the window is maximized, double-clicking the image enters full-screen; double-clicking again does not simply exit to the maximized window. Instead, it goes full-screen → normal size → maximized. I’m on Windows 11 22H2 build 22621.105; I’m not sure if this is a system quirk. Could you try to reproduce it?

This is the expected behavior.
VIV cannot change between fullscreen and maximized. (it's a Windows limitation)
VIV has to go back to the normal window then change the maximized/fullscreen state.

It's on my TODO list to "fix".
I have been messing with a few ideas to hide the transition.
It's likely going to be showing a temporarily secondary window.

Thank you for the suggestions.

[KatieM]

I have a photos folder with over 100,000 images in it. When I search for something like "Jane" in the name of the photo I would like to open a slideshow with only "Jane" playing. As it is now Image Viewer slideshow will play all 100,000 files, not just "Jane" like I want.
Is there a way to do this?

[void]

voidImageViewer navigates the images in the same folder. (not the search result list)

Please try drag-dropping your search results to voidImageViewer.

[therube]

Or set up a context-menu "Send To" item for VIV.

Or, if you're using Everything 1.5, you can set up a hotkey, say Alt+I, that opens the selected images into VIV.
So if you filter (search for) 'Jane' + Ctrl+A + Alt+I, you'll be visiting, "jane".

[emeyedeejay]

I just found this and love it - it's definitely my default image viewer now. Reminds me of the very early versions of ACDsee whchi was fab until it just became bloat.

Is it possible to add a directory/folder tree view?

TIA!

[void]

I will consider a treeview.
Thank you for the suggestion.

For now, please try File -> Open Folder. (Ctrl + B)

[sauljhl]

ah nostalgia, anyone remember infranview, is that still dev'd?
Def installing this and give feedback if any issues et al.

[hitm4n]

Hi. Really nice imageviewer i stumbled on today. I use "Everything" already to search across my drives but today i saw you made this imageviewer too so i figured i'd give it a go. Seeing as i'm still using ACDSee v3.01 from 2000 (i kid you not).

Anyway, in the transition, ACDSee used space and delete to go forward and backward through images. Your tool is using left and right arrow keys. I can get on board with that.

But... In ACDsee i was able to double click an image, and it would auto load, scaled up or down to fit and be in fullscreen mode. Is there a way to auto open a newly clicked image in fullscreen scaled to fit?

And when i'm done viewing that image, or flicking through multiple images in fullscreen mode, i could then just hit escape back to windows. The UI closed fully. Seems your tool exits fullscreen mode back to UI and then i have to either Ctrl Q or use the menu to quit.

Forgive me if this is already possible and i've missed it (let me know how please). If not, maybe you can consider these as options in next version. Thanks for a wonderful tool. ACDsee is dead

[void]

Thank you for your feedback.

Anyway, in the transition, ACDSee used space and delete to go forward and backward through images. Your tool is using left and right arrow keys. I can get on board with that.

Keyboard shortcuts can be customized under View -> Options -> Controls -> Navigate | Next / Navigate | Previous.

But... In ACDsee i was able to double click an image, and it would auto load, scaled up or down to fit and be in fullscreen mode. Is there a way to auto open a newly clicked image in fullscreen scaled to fit?

There's no UI option to do this.

It can be done via the registry:
From the Start menu, search for:

regedit

In the Registry Editor, navigate to:

HKEY_CURRENT_USER\Software\Classes\voidImageViewer.png\shell\open\command

add -fullscreen to the end of the (default) value.
For example:

"C:\Program Files\voidImageViewer\voidImageViewer.exe" "%1" /fullscreen

Do the same for HKEY_CURRENT_USER\Software\Classes\voidImageViewer.jpg\shell\open\command (and other extensions you use)

And when i'm done viewing that image, or flicking through multiple images in fullscreen mode, i could then just hit escape back to windows. The UI closed fully. Seems your tool exits fullscreen mode back to UI and then i have to either Ctrl Q or use the menu to quit.

Add the ESC key to View -> Options -> Controls -> File | Exit

[hitm4n]

Many thanks for the assistance.

I tried the reg thing, and like you say, looks like thats broken. It just doesn't launch fullscreen. A double click on the image takes me into fullscreen and then the left and right arrows move me back and forth (i'm getting used to using these new keys, i can't stay stuck in the year 2000). Launching fullscreen might be a nice option to have though if you can fix it, i can't be the only one that would like it

And unfortunately, adding ESC to Exit didn't quite work either. It does exit fullscreen, but goes back to UI still. And then it does exit the UI. A quick double tap of escape gets me out fully from fullscreen, so its workable.

Do you have anywhere to donate? KoFi, Patreon maybe? I'm using 2 of your apps now, you've supported me on day one and that deserves support back. It might not be much (not won lottery yet - i probably should start doing it).

[void]

I will have -fullscreen fixed in the next viv update.
I will have a viv update soon.

If you would like to support viv, please consider donating.
Thank you for your support.

[void]

I went to add -fullscreen, but viv doesn't use - command line switches, it uses / command lines switches.

Please try the reg mod above with

/fullscreen

[hitm4n]

Brilliant.

/fullscreen tagged on the end worked a treat so i've added that now to all the image formats listed in registry.

I added escape to the exit command too, so a quick double tap on that exits fullscreen then exits the app fully. I can get used to that.

Thanks for the help.

[void]

voidImageViewer-1.0.0.14.x64.en-US-Setup.exe (268 KB)
voidImageViewer-1.0.0.14.x86.en-US-Setup.exe (253 KB)
voidImageViewer-1.0.0.14.x64.en-US.zip (187 KB)
voidImageViewer-1.0.0.14.x86.en-US.zip (166 KB)
voidImageViewer-1.0.0.14.ARM64.en-US.zip (171 KB)
voidImageViewer-1.0.0.14.ARM.en-US.zip (178 KB)
voidImageViewer-1.0.0.14.sha256 (1 KB)
voidImageViewer-1.0.0.14.src.zip (4263 KB)
https://github.com/voidtools/voidImageViewer/

Tuesday, 16 December 2025: Version 1.0.0.14

• fixed an issue with webp using the wrong background color.
• fixed an issue with tracking the center of the image when resizing.
• fixed an issue with rendering images larger than 65536x65536.
• fixed an issue with screen saver not being prevented in slide show mode or when there is an animation.
• improved rendering performance.
• improved zooming of small images when going fullscreen.
• move window action will now scroll if zoomed.
• re-enabled WEBP_MSC_SSE41
• added title_bar_format ini setting.
• added System.Photo.Orientation support.
• added - command line switch support. Escape with "" or include a . in your switch.

This version will now support

-fullscreen

as expected.

[majunbo]

voidImageViewer软件缺少功能：
1、图片旋转功能；
2、图片打印功能，打印可以同时打印多个图片之类的；

The voidImageViewer software lacks the following features:
1.An image rotation function;
2.An image printing function, such as the ability to print multiple images at the same time.

[void]

要旋转图像，请在“编辑”菜单中单击“顺时针/逆时针旋转”。
voidImageViewer 仅支持使用 Windows 自带的打印对话框打印单张图像。
打印多张图像超出了 voidImageViewer 的功能范围。

感谢您的建议。



To rotate an image, from the Edit menu, click Rotate Clockwise/Counterclockwise
voidImageViewer will only support printing one image using the stock Windows print dialog.
Printing multiple images is beyond the scope of voidImageViewer.

Thank you for the suggestions.

[santilli]

Here are a few suggestions from my first time using it just today:

I noticed that the app sorts by date-modified by default, as opposed to alphabetically, which is counterintuitive imo. I thought there was an issue with how it handled numbers in filenames before noticing that it was just the default sorting option.

I could not see anywhere in the UI how many images are present in the current folder, and the position of the current file. Something like "37/50 files" in the window title would be enough.

Another thing I think is important and I don't see anywhere in the UI, is the current zoom level. Also, it would also be useful to have a zoom lock option, so if I am currently at 200% zoom, switching to a different image would preserve the current zoom level.

As for the controls, I like that they are customizable, but it could be even more. Some options are locked to specific buttons: I can decide to scroll with the left button or do something else... But if I want to scroll with the, wait for it, scroll wheel, it's not there

I like to make use of the keyboard+mouse combination so being able to take different actions with the scroll wheel by using a CTRL+scroll or Shift+scroll combo would be fantastic. With that I could use the scroll wheel to navigate through files, change the zoom and scroll through the current image swiftly.

And my biggest appeal, the best thing I could ever ask for, would be a bottom panel with thumbnails to facilitate navigation.

Still on the navigation subject, it would be neat having the option to lock navigation so it won't loop files, stopping navigation from going prior to the first or past the last file.

Thank you for putting this much work into apps that make our lives easier, mr tools.

[void]

Thank you for your feedback santilli,

I noticed that the app sorts by date-modified by default, as opposed to alphabetically, which is counterintuitive imo. I thought there was an issue with how it handled numbers in filenames before noticing that it was just the default sorting option.

The sort can be set from Navigation -> Sort -> Name
The default is to sort by date modified.

I could not see anywhere in the UI how many images are present in the current folder, and the position of the current file. Something like "37/50 files" in the window title would be enough.

I will consider showing this information in the Jump To window (J)

Another thing I think is important and I don't see anywhere in the UI, is the current zoom level. Also, it would also be useful to have a zoom lock option, so if I am currently at 200% zoom, switching to a different image would preserve the current zoom level.

The zoom levels are not nice round numbers like 200%
I will consider an option to show the zoom in the status bar and an option to make zooming persistent.

As for the controls, I like that they are customizable, but it could be even more. Some options are locked to specific buttons: I can decide to scroll with the left button or do something else... But if I want to scroll with the, wait for it, scroll wheel, it's not there

There's a scroll wheel action at the top on the Controls option page.

I like to make use of the keyboard+mouse combination so being able to take different actions with the scroll wheel by using a CTRL+scroll or Shift+scroll combo would be fantastic. With that I could use the scroll wheel to navigate through files, change the zoom and scroll through the current image swiftly.

I will consider an separate action for Ctrl + mousewheel.

And my biggest appeal, the best thing I could ever ask for, would be a bottom panel with thumbnails to facilitate navigation.

I will consider a thumbnail pane at the bottom.

Still on the navigation subject, it would be neat having the option to lock navigation so it won't loop files, stopping navigation from going prior to the first or past the last file.

I will consider a start and end marker.
Thank you for the suggestions.

[void]

voidImageViewer-1.0.0.15.x64.en-US-Setup.exe (268 KB)
voidImageViewer-1.0.0.15.x86.en-US-Setup.exe (253 KB)
voidImageViewer-1.0.0.15.x64.en-US.zip (187 KB)
voidImageViewer-1.0.0.15.x86.en-US.zip (166 KB)
voidImageViewer-1.0.0.15.ARM64.en-US.zip (171 KB)
voidImageViewer-1.0.0.15.ARM.en-US.zip (179 KB)
voidImageViewer-1.0.0.15.sha256 (1 KB)
voidImageViewer-1.0.0.15.src.zip (4263 KB)
https://github.com/voidtools/voidImageViewer/

Monday, 12 January 2026: Version 1.0.0.15

• fixed an issue with scrolling large images.
• improved position offset when using numpad keys.

[Seryi]

[void]

Thank you for the virus report Seryi,

voidImageViewer doesn't contain any viruses, malware, spyware or adware.

I will send Windows Defender a false positive report.

[NotNull]

Command:

Code: Select all

"voidImageViewer.exe"  "C:\Windows\Web\Screen\img100.jpg"  "C:\ProgramData\Microsoft\Windows NT\MSScan\WelcomeScan.jpg"  "C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\DesktopSpotlight\Assets\Images\image_0.jpg"  "C:\Windows\SystemApps\MicrosoftWindows.Client.CoreAI_cw5n1h2txyewy\DiscoveryOverlay\Assets\FirstRunExperience\FirstRunExperienceEdgySettings_LIGHT.png"  "C:\Windows\SystemResources\Windows.UI.ControlCenter\Assets\Images\StudioEffectsBackgroundBlur_Color.gif"  "C:\Windows\Web\4K\Wallpaper\Windows\img0_1920x1200.jpg"

These images should be on each Win11 system. Note that each picture comes from a different folder.

After loading, viv navigates only through images located in the folder of the first specified image ( "C:\Windows\Web\Screen\" ).
Expected: all specified images in the command-line will be shown.

[NotNull]

Updated to the latest version (1.0.0.15 x64) and all works as expected.

"Problem" solved!

Leave it here as it might help others.

[Qtax]

Been using Everything for years, but just found this and tested it out a but. Seems to work great!

A feature request:

A setting for keeping the current zoom and pan position when navigating to the next/pervious image (or deleting an image).

This is really useful when comparing burst of photos to see which ones are in focus and which could be deleted.

Is this something that you could consider adding, or would accept a PR for?

[void]

I will consider an option to not reset the zoom when the image changes.
Thank you for the suggestion.

For now, it can be done with NumPad 9, but your limited to 3x zoom and panning needs to be done with Ctrl + Numpad 2/4/6/8.

[xpclient]

I just found this fast and great little image viewer and have been using it with the "Allow multiple instances" option checked. I have a tiny feature request. I often have some images open in multiple instances and then while in the middle of my work for days/weeks from hibernating/sleep, I have to reboot Windows. Now Windows comes with some Application Restart API where we can save the session/command line of open apps. Apps simply need to register with it ( https://learn.microsoft.com/en-us/windo ... _recovery/ ) and on next boot, they reload automatically if the shutdown/restart is done with shutdown /t 0 /g switch.

For those apps which don't register for restart, on Windows 10 newer versions we can check "Register this program for restart" on the Compatibility tab and then it reloads automatically.

Now the only thing left is the work of restoring the last open file or session that the app must do.

So would it be possible for voidImageViewer to automatically restore/reload the last open image that was open? As a preference maybe? It would be very useful and time saving across reboots instead of remembering which images were open and reloading from the jumplist or Windows MRU list.

Currently apps like Notepad++ use this to automatically reload the last open text file at next startup. Or it can have such a behavior: if Void Image Viewer was closed by the user before reboot then restore nothing when VIV is started. But if it was running with some images open when Windows reboot was initiated, then reopen with that session

[void]

viv will never remember the last image or keep history by default.

I will consider an option to do this.
Thank you for the suggestion.

[therube]

Just babbling...

C:/out/sed/
¿ sed2hZFeo
¿ seduction - david arkenstone.mp3
¿ sed_go1_2015
¿ VIV_crash.7z
|
¿ <no picture files in this directory>
¿
¿¿¿¿pics
¿ ccc.png
¿ Everything - dupe -e.png
¿ Everything - dupe -r.png
¿ Everything - dupe.png
¿ Everything - es.ini - ES search of es.ini started working, why.png
¿ Everything - es.ini - same search in Everything.png
¿ Everything - ncmain dupe-size-sha1 offline.png
¿ Everything - result list, shaded focus.png
¿ Everything - SendTo dragdrop CustomCommands LFN SFN.png
¿ Salamander - how can i have two directories with the very same name.png
¿
¿¿¿¿unk
¿ def.tif
¿ def2.xyz
¿ def3.xyz
¿
¿¿¿¿X
¿ abc.jpg
¿ def.xyz
¿ xxx.png
¿ yyy.png
¿
¿¿¿¿Z
¿ zzz.png
¿
¿¿¿¿4
444.png


PIC.exe
- opens PIC, nothing more

PIC.exe .
- find files in the <current directory> + subdirectories

PIC.exe ..
- find files in the <parent directory> + subdirectories

PIC.exe * (PIC.exe *.*)
- does the same as PIC.exe ..
+ MORE ...
- parent (..) files & subdirectories are found, 1x
- all other files <current directory> & below, are found, 2 additional times, so a total of 3x
i suppose that * resolves to ... maybe (?)
(..) [1x] & (.) [1x] & (../.) [1x] & (something else another) [1x] (?)

PIC.exe <fullpath> (c:/out/sed, c:/out/sed/)
PIC.exe <relative-path> (x/z, x/z/)
- finds files in <path> + subdirectories

PIC.exe <wildcard> (*.png)
- find <wildcard> files - in the <current directory> - ONLY
- only a /single/ wildcard can be provided
- only the specified <wildcard> type files are found
- they are found regardless of them being a known file type to PIC
- multiple wildcards cannot be provided, *.png *.jpg *.xyz

PIC.exe <name> (xxx.png)
- displays <name> & loads any other pic: files in the <current directory>
PIC.exe <path>/<name> (c:/out/sed/pics/x/xxx.png)
- displays <name> & loads any other pic: files in the <specified directory> (c:/out/sed/pics/x/)

PIC.exe <names> (xxx.png yyy.png)
PIC.exe <path/names> (xxx.png abc.jpg z/zzz.png c:/out/sed/pics/x/xxx.png)
- only the specified files are loaded

forward slashes (/) are not supported
- but will work with <path> <relative-path>
- will not work with wildcards - all the time, but might, if the last path-marker is a backslash
c:/out/sed/pics/x/*.png - works
c:/out/sed/pics/x\*.png - works
c:/out/sed/pics/x/z/*.png - FAIL
c:/out/sed/pics/x/z\*.png - works
C:\>pic c:/out/sed/pics/*.png - FAIL
C:\>pic c:\out\sed\pics\*.png - works
suppose that / works at all is a quirk? suppose that / just should not be used.
- cannot use an opening / in a <relative-path> (/x/z/), as it is treated as if it were a switch

PIC.exe <relative-path/name> (x/xxx.png) [with forward slashes (/) - diff from above, with \'s]
- displays <name> + loads <path>
- <name> will only be loaded once, never again, as you advance (Next) through the files in <path>
- <name> is not shown in Jump To
so it /displays/ x/xxx.png & loads <current directory> into Jump To,

only known file types are found: (bmp|gif|ico|jpeg|jpg|tif|tiff|webp)
- unless specific <wildcard> or <name> is provided, in which case it will look for
- that file extension / name, regardless of what it might be (*.xyz, def.xyz)
- in the former case (*.xyz), only .xyz files will be found
- in the latter case (def.xyz), def.xyz will display + known file types in <current directory>

some Opens are potentially "dangerous" (or at least potentionally time consuming)
- like, PIC.exe *, from root: (C:\), as it will read your entire directory tree

multiple <paths> can be provided, multiple <names> can be provided,
but not multiple wildcards (*.jpg *.png), nor a combination of <path/wildcard> + <path>
c:\out\sed\pics\x\ c:\out\sed\pics\unk - OK
c:\out\sed\pics\x\*.png c:\out\sed\pics\unk - loads /unk/, but not /x/*.png
xxx.png yyy.png - OK
*.png *.jpg - FAIL

(oh, there are plenty of nuances, /most/ of my original testing /was/ with forward-slashes,
& they can throw a question into everything

i guess the biggest issue is i'm [still] not sure what to do when i want a particular
outcome?

like i want to search for all *.tif within c:/bin + subdirectories...
like i'm wanting a -r switch... -r c:/bin/ *.tif
suppose; pic c:/bin/, then Jump To '.tif' [not *.tif], & depending on the number of .tif,
it wouldn't really be feasible)

[void]

Thank you for the feedback therube,

wildcard support is on my TODO list (high priority)
wildcards are currently not supported.

I have added to my TODO list:
review '/' support
allow ESC to cancel recursive directory scans when loading *.jpg from c:

[Pseudoryx]

Can I ask where the file type association of the viewer is stored in the registry? I have not used the viewer for a long time but it is still shown persistently in the "Open With" context menu.

[void]

The associations are stored in the following registry keys:

Code: Select all

HKEY_CURRENT_USER\SOFTWARE\Classes\voidImageViewer.bmp
HKEY_CURRENT_USER\SOFTWARE\Classes\voidImageViewer.gif
HKEY_CURRENT_USER\SOFTWARE\Classes\voidImageViewer.ico
HKEY_CURRENT_USER\SOFTWARE\Classes\voidImageViewer.jpeg
HKEY_CURRENT_USER\SOFTWARE\Classes\voidImageViewer.jpg
HKEY_CURRENT_USER\SOFTWARE\Classes\voidImageViewer.png
HKEY_CURRENT_USER\SOFTWARE\Classes\voidImageViewer.tif
HKEY_CURRENT_USER\SOFTWARE\Classes\voidImageViewer.tiff
HKEY_CURRENT_USER\SOFTWARE\Classes\voidImageViewer.webp

These keys can be deleted.
Run regedit as a standard user when deleting these keys.