Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

Search the Community

Showing results for tags 'bug'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • The General Stuff
    • Announcements
    • Introduce Yourself!
    • General Discussion
  • Microsoft Software Products
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Server 2008/2012/2016
    • Older Windows NT-Family OSes
    • Windows 9x/ME
    • Other Microsoft Products
  • Unattended Windows Discussion & Support
    • Unattended Windows
    • Other Unattended Projects
  • Member Contributed Projects
    • Nuhi Utilities
    • Member Projects
    • Other Member Contributed Projects
    • Windows Updates Downloader
  • Software, Hardware, Media and Games
    • Forum Categories
    • Mobile Devices
  • Customizing Windows and Graphics
    • Customizing Windows
    • Customizing Graphics
  • Coding, Scripting and Servers
    • Web Development (HTML, Java, PHP, ASP, XML, etc.)
    • Programming (C++, Delphi, VB/VBS, CMD/batch, etc.)
    • Server - Side Help (IIS, Apache, etc.)
  • X's Concepts
  • The Compaq Computer Corporation Club's Discussion


There are no results to display.

There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL





Found 11 results

  1. While StartIsBack++ is running, there is a bug when trying to switch to a certain full screen application (a game called "World of Tanks"). Description When I click on the taskbar icon of that program to maximize it again while it is already running, there is a chance that the screen displays the program only for a tiny moment (less than half a second) and then it disappears again. The program is still running, it's not closed, but it's instantly minimized again so it's just not possible to switch back to it. Often I have to try four or five times to switch back to my full screen application until it stays in the foreground. Consequences This makes it impossible to use StartIsBack++ because I'm regularly running the application that StatIsBack interferes with. It is not possible to switch between applications which means that I cannot use my computer in the way a modern computer is meant to be used. Nowadays, nobody runs only a single program at a time. It needs to be possible to use more than a one program on your PC and to switch between programs. For usability, it is inacceptable that it takes up ten seconds to maximize an different application after quickly looking up something on the Internet for less than a minute. It is inacceptable as well that during the long process of trying to maximize my full screen application the screen flickers black (it always becomes black for a moment when switching to my full screen application, that's the usual behaviour that happens without StartIsBack, too) and white (website in the browser/desktop background) all the time. This causes headache and pain in the eyes and makes it harder to continue reading text on the screen without pain. Finding a solution I'm not sure if this bug is reproducable with other full screen applications. Maybe the problem only occurs when a program uses a certain kind of software or hardware to render the content of the screen (f.e. DirectX, OpenGL). Maybe it is down to the way a program renders the content on the screen, whether it uses the GPU or not, or whether it renders 3D models or a 2D surface. My game renders 3D scenery using the GPU. In conclusion it's hard to compare this behaviour to other programs and to reproduce the problem. Still this problem fundamentally destroys the usability of StartIsBack++ and therefore should be fixed because I think a software should claim to actually work. In conclusion I hope that this problem will be fixed. In order to do so, please tell whatever details are needed to find the root of the problem in StartIsBack++ and solve it. I hope the creators of StartIsBack++ are capable of making there program work. Thanks.
  2. Startisback 2.7.3 crash loops on my system, i am running 64-bit windows 10 1809 insider build 17758.1
  3. I am using an Unattend.xml file to install Windows 10. My .cmd file requires internet access during the Specialize pass. Windows 8\10 contains the network driver for my ethernet adapter, so there is no problem there. On Windows 8.1, this is no problem. On Windows 10 TH2 (last third? version) this is no problem On Windows 10 TH2 (first version) - there is no internet connectivity (e.g. ping www.bbc.co.uk does not work) On Windows 10 Anniversary (first version) - there is no internet connectivity (e.g. ping does not work) - I did not test the second release of TH2. In other words, Microsoft fixed the bug in TH2 but the bug is now back in the Anniversary build! It seems that there is no host name set up in the 'bad' versions (e.g. ipconfig /all shows no host name). I can 'fix' the problem by running msoobe for 10 seconds and then killing the task - I then get a host name and ping works. Does anyone know a better way of getting internet connectivity to work during the Specialize phase?
  4. Hello Bigmuscle and fellow Glass8 users! I run Windows 10 mit Glass8 on my Desktop PC, and since the anniversary update I have to randomly recurring problems with Glass8. 1. White window borders Normally, all is working fie, but on some windows starts I get white window borders instead of glassy ones. See attached screenshot. debug.log shows nothing out of the ordinary as far as I can tell. when this happens, DWM seems to run into some kind of memory leak as it grabs more and more RAM for itself. Normally it uses about 17-20MB, as you can see in the screenshot, I had already over 300MB allocated after maybe 15 minutes. I then restart windows and the issue is gone, glass is back and DWM runs normal. 2. Glass8 theme not applied This also happens randomly and more often than the first issue. According to the debug.log the standard theme (which I am using) is loaded, but the window border is just glass without a theme. I can either restart Windows or just apply the theme again using the GUI. Then the theme is loaded correctly. I tried the configure it using the GUI in admin mode, but that did not help. I also searched the registry with regedit related reg keys, as I have moved the install location. There was one key with the old path to the theme, which corresponded to a file not found error in the debug log where aerohost used the old path to the theme file. I have corrected this and the path is correct now, but the issue still randomly appears. Here it appeared directly after the reboot I did because of issue 1. Maybe someone has a clue or idea what could be the cause of this issues? I will gladly provide any information or logfile needed, just tell me what I have to do. Thanks! no_theme_debug.log white_windowframe_debug.zip
  5. Here I will outline a situation where you can corrupt a mount point and an image by using a system with multiple versions of DISM. We already know that there is some differences between the DISM that comes with Windows and the one in the WAIK/ADK (hereafter referred to as ADK). This difference is beyond the stock DISM not supporting all command line options. It is important to note this, as we do have the technical ability to have multiple ADK versions installed or by using JFX's Get WAIK Tools to skip the large download. NOTE: This applies to all versions of Windows and WAIK/ADK versions. This problem has 2 parts. One is recoverable, the other one is not 100%. There are 4 problems. Problem #1: Stock DISM is the default. DISM exists in c:\windows\system32. Even if you cd into say c:\adk10\ and that is where your DISM from ADK v10 is kept, if you just type DISM, Windows will execute the one in System32. You need to fully qualify the DISM command in order to execute the one you want. Problem #2: You can mix DISM versions interchangeably and it doesn't care. You have mounted an image with ADK DISM. You can then run commands using any other DISM, even if those versions do something different or do not fully support the mounted image. Problem #3: DISM doesn't know all the mount points. You can mount multiple images, or even nested images, but /CLEANUP-WIM shows that it does not know all the mount points. Problem #4: Windows protects files based on filename. You may have run into this situation before. You have a folder called Windows or Program Files somewhere that is not part of your booted OS, but Windows won't let you delete it. Recoverable Situation - Mount image using ADK DISM to c:\mount - Add-driver using stock DISM. In this scenario, stock DISM can't actually add a driver to the image, but it still tries. The DISM.exe process will start gobbling up memory. It will do this until the process crashes or your computer does. It also will lock the command prompt so that Ctrl+C will not cause the process to stop. You can kill the process and then clean-up the mount point. Unrecoverable/Corruption Situation - Mount image using ADK DISM to c:\mount - Mount nested image using ADK DISM to c:\mount2 - Add-driver using stock DISM. In this scenario, we wanted to add a driver to a nested wim. One example of a nested wim could be winre.wim. Here, the same as the last scenario happens, DISM can't add the driver and starts incrementing RAM usage. DISM process goes away (crash/kill process) then you can run /CLEANUP-WIM, but only mount2 is cleaned up. Here is what happens next: 1. c:\mount still has the mounted image in it. 2. DISM /CLEANUP-WIM doesn't see it as a valid mount point. 3. DISM /UNMOUNT /DISCARD gives you an error. 4. You can't delete everything in the folder because of Windows file protection. 5. You can't remount your image to another folder because DISM says that index is already mounted. You can get past the issue by never using that mount folder again, but you can rename it and probably move it somewhere else. I encountered the corrupt image situation just once (enough for me to make this thread) and played it safe by deleting the .wim file and restoring a backup and THEN rename the file. Even if you delete and restore, DISM will tell you the image is already mounted. If you rename it, then it can be mounted again to a new location. So just a word of caution for anyone using multiple ADK or DISMs on the same system to service images.
  6. In the title bar there is a noticeable gap/line/shadow above to minimize and maximize buttons. See photos below. I am running Windows 10 Build 10240 RTM. Personal Opinions I do not like the borders around windows. I prefer not to see them at all because they don't have that clean 1px line around the window look that Windows 10 has. The border looks terrible especially in the settings and any other windows that have a gray title bar. See photos below and you will know what I mean. I really do not like the border around the start menu either. The start menu does not need a border. This looks so much better. See photo below. Please remove the borders they are unnecessary. We are using Windows 10 now. The 1px borders that Windows 10 gives us are much cleaner looking. .
  7. So whenever I go into a fullscreen video, such as YouTube or Vessel, the start menu button showing. This is the same for border-less windowed games as well. The weird thing is that it just started happening a few days ago, after owning this program for 1 or so years. Is there any way this can be fixed and if not can this be patched? I hope I'm posting this to the right place. Thanks
  8. We know the bug in Windows 8.1 in certain dialogues (When delete a file/folder, copy…) Exploring a bit I discovered that deleting all icons size 256x256px in imageres.dll (and replace it) the bug go away. But it is exhausting eliminate about 300 icons for any app/soft. Any interested in investigating this error and solved? Another way to fix it's set the display/screen size (dpi) to 200% (maximum) , but it 's all a bit bigger in sight. * Sorry for my english.
  9. Hi there, I have a problem with Aero Glass 1.3.1 for Windows 8.1+. It's absolutly not working for me. Window buttons like close, minimize etc. are bugged and windows are white or black. The "window name" is displaying bad too. I'm using Win 10 technical preview build 9879. Because screenshot was so big, I've uploaded it to pasteboard, there is it: http://pbrd.co/1sKBJdr I was trying to reinstall it a lot of times, still this problem. Anyone who know how to fix this?
  10. So, I'm using Bearwindows's VBEMP 9x driver on Windows 98. I was installing a driver for another piece of hardware that I have, when the installer decided to open up a DOS box and gave me the funny colors on the screen. Usually I can press Alt+Enter to enter full screen and work around the bug, but not this time. I tried closing out the window with Alt+F4 and minimizing all windows with WinKey+D, and nothing worked. Every time I reboot, the box pops up again right after I log in, and messes up my screen, so I can't see anything of what's going on. I tried to reboot into safe mode and disable the VBEMP driver, but safe mode disables not only my graphics driver, but my mouse and keyboard drivers along with it, so I can't do anything. Any workarounds? I know I can set the DOS prompt to open in full screen, but I forgot about it. Is there a way to temporarily disable the graphics driver while in DOS mode?
  11. http://unattended.msfn.org/ is giving a 403.

  • Create New...