Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


thepwrtank18

Member
  • Content Count

    14
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

2 Neutral

About thepwrtank18

  • Birthday December 3

Profile Information

  • OS
    Windows 10 x64
  • Country

Flags

  • Country Flag

Recent Profile Visitors

73 profile views
  1. When I try to mount anything, I get this error: Input string was not in a correct format. A more detailed error message is here: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.FormatException: Input string was not in a correct format. at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at System.Convert.ToInt32(String value) at �.�.�(String& ) at �.�. () at �.�.�(Int32 ) at �.�.�(Boolean ) at �.�.�(Object , EventArgs ) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9136 (WinRelRS6.050727-9100) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- vlite Assembly Version: 1.2.0.2 Win32 Version: 1.2.0.2 CodeBase: file:///C:/Program%20Files%20(x86)/vLite/vLite.exe ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9136 (WinRelRS6.050727-9100) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- vLite Assembly Version: 1.2.0.2 Win32 Version: 1.2.0.2 CodeBase: file:///C:/Program%20Files%20(x86)/vLite/vLite.exe ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9136 (WinRelRS6.050727-9100) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9136 (WinRelRS6.050727-9100) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- MCDBNET2 Assembly Version: 1.3.3.33894 Win32 Version: 1.33.0.133 CodeBase: file:///C:/Program%20Files%20(x86)/vLite/MCDBNET2.DLL ---------------------------------------- msvcm80 Assembly Version: 8.0.50727.9659 Win32 Version: 8.00.50727.9659 CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9659_none_d08cfd96442b25cc/msvcm80.dll ---------------------------------------- vhelper Assembly Version: 1.0.3166.20582 Win32 Version: 1, 0, 0, 1 CodeBase: file:///C:/Program%20Files%20(x86)/vLite/vhelper.DLL ---------------------------------------- msvcm90 Assembly Version: 9.0.30729.1 Win32 Version: 9.00.30729.1 CodeBase: file:///C:/Program%20Files%20(x86)/vLite/msvcm90.DLL ---------------------------------------- System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9136 (WinRelRS6.050727-9100) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
  2. I'll see if this works. Thanks!
  3. Is it possible to install MSU updates in bulk? I have a lot of updates to install.
  4. According to Microsoft's Product Lifecycle FAQ: Windows Server 2008 gets ESU updates until January 10, 2023. This means that if we could get Windows Vista to: Accept updates for Windows Server 2008 (already done), and Accept ESU updates for Windows Server 2008, We would get support until January 10, 2023.
  5. According to Microsoft, the end date for Windows 7 ESU updates is January 10, 2023. The end date for POSReady 7 is October 12, 2021. And look at this: If you apply ESU to POSReady, you get updates until October 14, 2024! If we were able to trick Windows Update to thinking Windows 7 supports ESU and POSReady, that would mean an extra 4 years of support! And provided that Windows Server 2008 has extra support, it also has up to January 2023, meaning more support for Vista, and if we apply Embedded updates, that means more time! Although considering Windows Vista support ended for Windows Update, that would probably not happen.
  6. Would it be possible to slipstream updates to Office 2010?
  7. Yeah, Windows Update broke because they killed SHA-1. I do see that it's for security reasons, but most likely it's just to add insult to injury for the Vista / XP community.
  8. As of August 2020, Windows 2000, XP and Vista are no longer downloadable via Windows Update. How? Windows Update's servers have used SHA-1 and SHA-2 for a while now. As of August 2020, Microsoft has transitioned from SHA-1 to SHA-2 completely, removing SHA-1 support (which 2000, XP, and Vista need). Why? Security reasons. SHA-1 is more vulnerable to security risks. As an alternative to Windows Update, you will need to use this Update Repository: You can also use Server 2008 updates, which you can find here: https://mega.nz/folder/txxRyLzC#1vBMGzMHiL864f3bl1Rj1w (created by @greenhillmaniac)
  9. Unfortunately, there is no solution to this problem. This occurs because Microsoft cut SHA-1 signing from Windows Update, so Windows Update on Windows 2000, XP and Vista no longer work, and Windows 7 needs a manual update in order for Windows Update to work again. An alternative is:
  10. OS: Windows Vista x64 (no extended kernel)
  11. I keep getting error code 80244019 when I try to check for updates. Even after restarting and clicking "Try again", it shows the same error. I'm enrolled in Microsoft Update, if that is useful.
×
×
  • Create New...