KomuraSoft LLC
Consult us
Menu

Windows development & engineering support from KomuraSoft

Modification & Maintenance of Existing Windows SoftwareKeep the software that supports your business today going for the years ahead.

Add features, fix faults and improve performance while retaining familiar operations and reports. We start with the changes you need, rather than assuming a complete rewrite.

Discuss changes to your software See pricing & process

No specification document needed. You can consult us with whatever you know.

  • Work directly with an engineer
  • Consult us before requirements are finalized
  • Commission only the scope you need

You can consult us from stages like these

Start with the problem you need to solve.

Every change risks breaking something else

We check the scope of impact and existing behavior, and carry out the modification including testing and rollback.

The predecessor is gone, so no one can make changes

We help take over the software by examining the code, documentation and environments that remain.

It runs, but it is slow, unstable or difficult to update

We prioritize changes by their likely benefit and impact on operations.

Someone you can consult about technical matters, just as they are.

Profile photo of Go Komura

Representative & engineer

Go Komura

A Windows-focused engineer works with you from confirming your problem through investigation, design and implementation. Points you cannot yet fully explain are sorted out starting from the technical issues.

Experience & technologies / Company information

Published technical case study

Investigating a crash that occurs only after long operation

We tracked handle counts and added logs at processing boundaries, narrowing the investigation to a handle leak.

Read the problem and investigation approach

Scope of support

A focused task or a complete application.

From a specific investigation or change to end-to-end development, we agree on a scope that fits your situation.

Feature additions and modifications to existing Windows software

Feature additions, bug fixes and ongoing maintenance, after checking the current work procedures and dependencies.

64-bit support and architecture updates

Assessment and changes for x86-based systems and their dependencies, taking mixed 32-bit and 64-bit operation into account.

Incremental modernization

Update high-priority areas to a more maintainable design without assuming a complete replacement.

Examples of results and deliverables

  • Current architecture and change impact assessment
  • Updated software and validation results
  • Deployment and rollback guidance with maintenance notes

These are examples, depending on the work commissioned. We agree on the scope and format of deliverables when preparing the estimate.

Facing a similar challenge? Tell us where things stand.

Discuss changes to your software

No specification document needed. You can consult us with whatever you know.

Pricing and process

You do not need every detail decided to get started.

Start with an assessment and priority modifications

We check the source code and development environment, then agree on the behavior to preserve and the changes to make.

Pricing guide

Quoted according to the scope of modification and maintenance

We consider the features, dependencies, investigation required and scope of ongoing maintenance before proposing the work.

The free scope of initial feasibility checks, and paid engagements

On the understanding that you will commission the full development if we judge it feasible, the initial investigation needed for the estimate and for our decision on whether to accept the order is free in principle. Extended validation, dedicated environments, prototypes, proofs of concept, delivery of detailed investigation reports and the like may require a paid engagement.

An investigation or review commissioned in its own right is quoted as a separate paid service. We explain the scope and cost before any paid work begins.

  1. Tell us about the situation

    Share your goal, the problem and the environment, as far as you know them.

  2. Review the scope and cost

    We outline the investigation needed, scope, deliverables, cost and proposed process.

  3. Agree before work begins

    During the investigation and development, we share progress, confirmed findings and remaining constraints.

  4. Review the results and handover

    We validate the results under agreed conditions and prepare for deployment or the next step.

Need more technical detail?

Explore technologies and the detailed approach

Keep familiar Windows software working for the years ahead.

Software that is essential to the business cannot simply be rebuilt overnight. KomuraSoft examines its functions and operating conditions before making changes or taking on maintenance. We do not assume a full replacement: the scope follows the expected benefit and impact.

Challenges you can consult us about

  • Add features while preserving current operations and reports.
  • Review the architecture because each change seems to cause another fault.
  • Improve slow operation or instability after extended use.
  • Address 32-bit assumptions or old components that obstruct environment upgrades.
  • Looking for someone to consult about future modification and maintenance, for example because the person in charge has left the company.

Changes and maintenance we support

We work on existing applications such as VB6, MFC and WinForms, including feature additions, bug fixes, performance improvement and code organization. Systems combining COM, ActiveX, OCX, C++ and C# are assessed with their dependencies in mind.

For 64-bit support or architectural updates, we check not only the application but also its DLLs, registration, permissions and deployment environments. We strengthen logging and tests where needed so that the effects of changes are easier to trace.

An approach that keeps the impact on current operations low

The key is to define the behavior that must stay the same, not just the parts that will change.

  1. Understand the current system. We review workflows, dependencies, development and deployment environments, and known problems.
  2. Narrow the scope of modification. We agree on priorities and impact, identifying what to retain and what to change.
  3. Prepare validation. We establish regression checks, logs and, where needed, rollback procedures.
  4. Introduce changes in stages. We validate each change and plan deployment around operating conditions.

Not sure whether to modify or replace it?

Whether to keep improving the current software or build a replacement depends on its maintainability and expected period of use. We can investigate first and distinguish what can be addressed through changes from what merits replacement.

For a move centered on a new application, see Windows app replacement. When you consult us, tell us what is difficult about the current software and whether its source, specification and development environment are available.

Questions before commissioning work

Can you modify older Windows software?

You can consult us about existing software such as VB6, MFC or WinForms applications. We check the source code, development environment and dependent components to establish what can be changed and what preparation is needed.

Can we improve only the necessary parts before considering a rewrite?

Yes. We can work on priority fixes and features while keeping the current application in use. We agree on the change scope, functions to validate and rollback approach beforehand.

Can you help without a specification or the person who was in charge at the time?

Yes. We begin with the remaining documents, code and actual behavior, separating known specifications from areas that need further investigation.

Get in touch

A few lines about your situation are enough.

You do not need a detailed specification or technical terminology. Share what you know about:

  • The problem or the outcome you need
  • The software, devices and operating environment
  • Your preferred timeframe, even if it is not decided

There is no need to send confidential documents or passwords with your initial inquiry.

Example consultation message

We need to add features to a Windows application, but its original developer is unavailable. We would like help starting with an assessment of the existing software.
Discuss changes to your software Consult us by email

No specification document needed. You can consult us with whatever you know.

The discussion button opens our English contact page with ways to get in touch. “Consult us by email” creates an email that includes the service name.

Browse related technical articles